npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

omxc-workflow

v0.1.2

Published

Multi-agent orchestration layer for CoPilot CLI

Readme

omx-copilot

OMX-CoPilot is a workflow layer for GitHub Copilot CLI.

It keeps Copilot CLI as the execution engine and makes it easier to:

  • start stronger sessions by default
  • run one consistent flow from clarification to completion
  • invoke canonical workflows with $deep-interview, $ralplan, $team, and $ralph
  • keep project guidance, plans, logs, and state in .omx/

Reference And Attribution

This repository is a Copilot CLI-focused fork and adaptation of the original project:

  • https://github.com/Yeachan-Heo/oh-my-codex.git

This README's product framing and usage model are authored for OMX Copilot usage, and are informed by these sources:

  • OMX runtime contract and orchestration policy in AGENTS.md
  • OMX command surfaces and behavior in src/cli/index.ts
  • Existing OMX docs set in docs/getting-started.html and docs/skills.html
  • Legacy website/docs sources (historical reference, may be outdated/unavailable):
    • https://yeachan-heo.github.io/oh-my-codex-website/
    • https://yeachan-heo.github.io/oh-my-codex-website/docs.html

This fork keeps compatibility paths such as .codex/ and CODEX_HOME where required by runtime behavior, while adapting workflows for GitHub Copilot CLI.

Legacy Team Listings (Historical Reference)

These listings are preserved as historical reference only.

New Usage Guide

0) Install From npm (Recommended)

npm install -g omxc-workflow
omxc setup
omxc doctor

1) Clone And Install Dependencies (Source Only)

git clone https://github.com/krisadas/omx-copilot
cd omx-copilot
npm install
npm audit fix
npm run build

What this does:

  • installs local dependencies
  • builds dist/ outputs from this source tree
  • prepares runnable local CLI entrypoint at dist/cli/omx.js

2) Initialize Runtime Assets From Source Build

omxc setup
omxc doctor

Equivalent source-tree direct commands:

node dist/cli/omx.js setup
node dist/cli/omx.js doctor

3) Start A Session (From This Source Tree)

Default interactive session:

omxc

High reasoning + permissive approvals (trusted environments only):

omxc --high --madmax

Detached tmux leader session:

omxc --tmux --high --madmax

4) Use The Core Flow In Session

Use this sequence for most complex work:

$deep-interview "clarify requirements and boundaries"
$ralplan "approve architecture, risks, and tests"
$ralph "execute end-to-end with verification"

When execution is parallelizable, switch to team mode:

$team 3:executor "implement approved plan in parallel lanes"

5) Daily Command Patterns (Source Build)

Repository exploration:

omxc explore --prompt "find where worker launch args are normalized"

Bounded shell verification:

omxc sparkshell git status
omxc sparkshell --tmux-pane %12 --tail-lines 300

Team runtime operations:

omxc team 4:executor "fix build and failing tests"
omxc team status <team-name>
omxc team resume <team-name>
omxc team shutdown <team-name>

6) Runtime Model

Think of OMX in three layers:

  • Copilot CLI runs the core agent execution
  • OMX adds orchestration workflows and guardrails
  • .omx/ persists plans, state, logs, and runtime metadata

7) Environment Requirements

  • Node.js 20+
  • GitHub CoPilot CLI installed and authenticated in your environment
  • tmux on macOS/Linux for team mode
  • psmux on Windows for native team mode

8) Operational Tips

  • Use npm run setup after upgrades to refresh managed assets
  • Use npm run doctor first when something looks inconsistent
  • Keep AGENTS.md in repo root for project-specific orchestration policy
  • Prefer $ralplan before $team/$ralph for large or risky changes

9) Known Startup Issue (Intel Mac)

If startup causes high syspolicyd / trustd CPU on Intel Macs:

  • run xattr -dr com.apple.quarantine $(which omxc) (if you also use a global install)
  • add your terminal to Developer Tools in macOS security settings
  • reduce launch aggressiveness (for example, skip --madmax --high)

Local Project References

Languages

Contributors

| Role | Name | GitHub | | --- | --- | --- | | Fork Owner & Maintainer | Krisada | @krisadas |

License

MIT