oh-my-codex is a workflow layer for OpenAI Codex CLI that adds prompts, agent teams, skills, hooks, HUDs, and other runtime assistance while leaving Codex as the execution engine. It is for people who use Codex CLI and want structured workflows and additional help as tasks become larger. The catalogue entries are its skills, hooks, and MCP integrations for those Codex workflows.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add Yeachan-Heo/oh-my-codex --skill plangit clone --depth 1 https://github.com/Yeachan-Heo/oh-my-codexWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/yeachan-heo/oh-my-codex/plan)<a href="https://agentmods.dev/skills/yeachan-heo/oh-my-codex/plan"><img src="https://agentmods.dev/badge/skills/yeachan-heo/oh-my-codex/plan/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/yeachan-heo/oh-my-codex/plan"><img src="https://agentmods.dev/badge/skills/yeachan-heo/oh-my-codex/plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00008 | $0.00899 |
| Opus 5.5 | $0.00003 | $0.00360 |
| Sonnet 5.5 | $0.00002 | $0.00180 |
| Haiku 4.5 | $0.00001 | $0.00090 |
Grade A, and why
plan scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
<Use_When>
- Planning before implementation — "plan this", "let's plan"
- Requirements are vague and need scoping — use
--interview - Reviewing an existing plan —
--review</Use_When>
<Do_Not_Use_When>
- Want direct execution — execute the scoped task directly; use
ultragoalonly for durable goals orteamfor coordinated parallel work - Simple focused fix with obvious scope — skip planning </Do_Not_Use_When>
<Execution_Policy>
- Auto-detect interview vs direct;
--interviewforces Socratic mode,--directskips it - Ask one question at a time; gather codebase facts first
omx exploreis deprecated. Use normal repository inspection for codebase facts;omx sparkshellonly for explicit shell-native evidence- Plans must be evidence-backed: 80%+ claims cite file/line, 90%+ criteria testable
- Right-size steps to scope; save to
.omx/plans/</Execution_Policy>
Mode Selection
| Mode | Trigger | Behavior |
|---|---|---|
| Interview | --interview or broad request |
Socratic requirements gathering |
| Direct | --direct or detailed request |
Generate plan immediately |
| Review | --review |
Critic evaluation of existing plan |
Interview (--interview)
- Classify request; ask one focused question via
omx question - Gather codebase facts first, then ask informed follow-ups
- Build on answers; consult Analyst for hidden requirements
- Create plan when user signals readiness
Direct
- Quick analysis (optional Analyst)
- Generate plan immediately
- Optional Critic review if requested
Review (--review)
- Read plan from
.omx/plans/ - Evaluate via Critic; verdict APPROVED/REVISE/REJECT
- If author == reviewer, hand off to
$code-review
Output
Every plan includes: Requirements Summary, Acceptance Criteria (testable), Implementation Steps (with file refs, adaptive count), Risks/Mitigations, Verification. Saved to .omx/plans/.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago Changed 4a2312fee52f
- 1mo ago First seen · 95 lines · 8 tokens per session scan A 31badb8a5a61
plan is a skill published in the GitHub repository Yeachan-Heo/oh-my-codex (33,629 stars, last pushed today), licensed MIT. It adds 8 tokens to every session and 899 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.