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 skillgit 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/skill)<a href="https://agentmods.dev/skills/yeachan-heo/oh-my-codex/skill"><img src="https://agentmods.dev/badge/skills/yeachan-heo/oh-my-codex/skill/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/skill"><img src="https://agentmods.dev/badge/skills/yeachan-heo/oh-my-codex/skill.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.00018 | $0.01094 |
| Opus 5.5 | $0.00007 | $0.00438 |
| Sonnet 5.5 | $0.00004 | $0.00219 |
| Haiku 4.5 | $0.00002 | $0.00109 |
Grade A, and why
skill 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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill Management
Manage local SKILL.md files with /skill commands. Shared execution, delegation,
state, hook, team, cancellation, verification, and escalation invariants live in
templates/AGENTS.md; follow that contract instead of repeating it here.
<Use_When>
- The user asks to list, add, edit, remove, search, inspect, sync, set up, scan, or validate skills.
- A durable, codebase-specific solution or workflow should be captured as a skill. </Use_When>
<Do_Not_Use_When>
- Use
/learnerto extract a skill from a conversation and/notefor a short note. - Do not use this prompt to change runtime code, catalogs, hooks, or installation logic. </Do_Not_Use_When>
Scopes and commands
Canonical roots are ${CODEX_HOME:-$HOME/.codex}/skills/ (user) and .codex/skills/
(project). A skill lives at <root>/<name>/SKILL.md.
| Command | Contract |
|---|---|
/skill list |
Scan both roots, parse frontmatter, and show name, description, triggers, scope, and quality/usage (N/A when unavailable). |
/skill add [name] |
Run the authoring wizard, validate the name, choose scope, create SKILL.md, and report its path. |
/skill edit <name> |
Find one scope, show metadata, then update description, triggers, argument hint, body, or rename and report the change. |
/skill remove <name> |
Find the skill, show scope and metadata, confirm explicitly, then remove its directory. |
/skill search <query> |
Case-insensitively search name, description, triggers, and body; rank name/trigger matches first and show context. |
/skill info <name> |
Show parsed metadata, scope, path, and full body; suggest /skill search when absent. |
/skill sync |
Compare user/project skills, show user-only/project-only/common entries, and confirm every copy or overwrite. |
/skill setup |
Ensure both roots exist, scan them, then offer add, list, pattern scan, import, or done. |
/skill scan |
Run setup's scan/inventory without its interactive menu. |
/skill validate |
Validate every skill in both roots and report each path's pass/fail result; never rewrite files. |
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 First seen · 112 lines · 18 tokens per session scan A bbd89ebc5adf
skill is a skill published in the GitHub repository Yeachan-Heo/oh-my-codex (33,629 stars, last pushed today), licensed MIT. It adds 18 tokens to every session and 1,094 once invoked, about $0.0001 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.