oh-my-codex (OMX)
Use this skill when you need multi-agent orchestration, team workers, persistent state, or OMX-specific read-only shell routing.
What It Covers
- Role prompts for
architect, planner, executor, debugger, verifier, explore, and the review/domain roles
- Workflow skills like
$autopilot, $ralph, $ultrawork, $team, $plan, $tdd, $build-fix, $code-review, $security-review, and $cancel
omx explore for read-only lookup
omx sparkshell for bounded shell summaries
omx adapt for external target adapter setup
- Persistent MCP servers for state, memory, code intelligence, and traces
Install & Refresh
npm install -g @openai/codex oh-my-codex
omx setup
omx doctor
If the repo or config changes later, rerun omx update or omx setup to refresh the shipped assets.
Common Usage
/prompts:architect "analyze current auth boundaries"
/prompts:executor "implement input validation in login"
/prompts:security-reviewer "audit OAuth flow"
$plan "ship OAuth callback safely"
$team 3:executor "fix all TypeScript errors"
$ralph "finish the refactor and verify"
omx team 4:executor "parallelize a multi-module refactor"
omx team status <team-name>
omx team shutdown <team-name>
Quick Reference
| Command |
Action |
omx |
Launch Codex with HUD |
omx setup |
Install prompts, skills, and config wiring |
omx update |
Refresh installed OMX assets |
omx doctor |
Installation/runtime diagnostics |
omx team <n>:<role> "<task>" |
Start team workers |
omx explore |
Read-only repository lookup |
omx sparkshell |
Bounded shell summaries |
omx adapt |
Adapter workflow for external targets |
omx status |
Show active modes |
omx cancel |
Cancel execution modes |
omx reasoning <mode> |
Set reasoning level |
omx hud |
HUD display options |
omx help |
Show help |
Notes
- Keep AGENTS.md injection enabled unless you have a strong reason to bypass it.
- Prefer
omx team only when parallel coordination actually helps.
- Use
omx --xhigh --madmax only in trusted environments.
1---2name: oh-my-codex3description: OMX multi-agent orchestration.4---56# oh-my-codex (OMX)78Use this skill when you need multi-agent orchestration, team workers, persistent state, or OMX-specific read-only shell routing.910## What It Covers1112- Role prompts for `architect`, `planner`, `executor`, `debugger`, `verifier`, `explore`, and the review/domain roles13- Workflow skills like `$autopilot`, `$ralph`, `$ultrawork`, `$team`, `$plan`, `$tdd`, `$build-fix`, `$code-review`, `$security-review`, and `$cancel`14- `omx explore` for read-only lookup15- `omx sparkshell` for bounded shell summaries16- `omx adapt` for external target adapter setup17- Persistent MCP servers for state, memory, code intelligence, and traces1819## Install & Refresh2021```bash22npm install -g @openai/codex oh-my-codex23omx setup24omx doctor25```2627If the repo or config changes later, rerun `omx update` or `omx setup` to refresh the shipped assets.2829## Common Usage3031```text32/prompts:architect "analyze current auth boundaries"33/prompts:executor "implement input validation in login"34/prompts:security-reviewer "audit OAuth flow"35```3637```text38$plan "ship OAuth callback safely"39$team 3:executor "fix all TypeScript errors"40$ralph "finish the refactor and verify"41```4243```bash44omx team 4:executor "parallelize a multi-module refactor"45omx team status <team-name>46omx team shutdown <team-name>47```4849## Quick Reference5051| Command | Action |52|---------|--------|53| `omx` | Launch Codex with HUD |54| `omx setup` | Install prompts, skills, and config wiring |55| `omx update` | Refresh installed OMX assets |56| `omx doctor` | Installation/runtime diagnostics |57| `omx team <n>:<role> "<task>"` | Start team workers |58| `omx explore` | Read-only repository lookup |59| `omx sparkshell` | Bounded shell summaries |60| `omx adapt` | Adapter workflow for external targets |61| `omx status` | Show active modes |62| `omx cancel` | Cancel execution modes |63| `omx reasoning <mode>` | Set reasoning level |64| `omx hud` | HUD display options |65| `omx help` | Show help |6667## Notes6869- Keep AGENTS.md injection enabled unless you have a strong reason to bypass it.70- Prefer `omx team` only when parallel coordination actually helps.71- Use `omx --xhigh --madmax` only in trusted environments.72