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 ultragoalgit 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/ultragoal)<a href="https://agentmods.dev/skills/yeachan-heo/oh-my-codex/ultragoal"><img src="https://agentmods.dev/badge/skills/yeachan-heo/oh-my-codex/ultragoal/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/ultragoal"><img src="https://agentmods.dev/badge/skills/yeachan-heo/oh-my-codex/ultragoal.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.00022 | $0.01087 |
| Opus 5 | $0.00011 | $0.00544 |
| Sonnet 5 | $0.00004 | $0.00217 |
| Haiku 4.5 | $0.00002 | $0.00109 |
Grade A, and why
ultragoal 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 12d 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ultragoal Workflow
When to use
Use for ultragoal, create-goals, complete-goals, durable multi-goal planning, or sequential execution over Codex /goal. Read AGENTS.md#durable-runtime-invariants-canonical-ssot for state ownership and goal-tool boundaries.
Inputs and preconditions
- Durable artifacts are
.omx/ultragoal/brief.md,.omx/ultragoal/goals.json, and.omx/ultragoal/ledger.jsonl. - New plans use aggregate Codex goal mode by default: one stable pointer objective for the plan while OMX tracks individual stories. Use
--codex-goal-mode per-storyonly when explicitly requested. - Do not call
/goal clearfrom shell or this skill. After a completed run, the operator may clear the interactive Codex goal in the Codex UI before another same-thread run.
Operational steps: create
Run one command, then inspect the generated plan:
omx ultragoal create-goals --brief "<brief>"
omx ultragoal create-goals --brief-file <path>
cat <brief> | omx ultragoal create-goals --from-stdin
omx ultragoal create-goals --codex-goal-mode per-story --brief "<brief>"
If refinement is needed, use explicit supported steering rather than editing durable artifacts by hand.
Operational steps: execute
Repeat until omx ultragoal status reports all goals complete:
- Run
omx ultragoal complete-goalsand read its handoff. - Call
get_goal. Callcreate_goalwith the printed payload only when no active Codex goal exists; otherwise continue the matching aggregate objective. - Complete one OMX story and audit its objective against real artifacts and verification evidence.
- For intermediate aggregate stories, keep the Codex goal active and checkpoint:
omx ultragoal checkpoint --goal-id <id> --status complete --evidence "<evidence>" --codex-goal-json <fresh-get-goal-json-or-path> - For a blocked/failed story, use
--status blocked|failedwith evidence; resume failed work withomx ultragoal complete-goals --retry-failed. - On the final story, complete the final gate below before
update_goal({status: "complete"}); then callget_goalagain and checkpoint the fresh complete snapshot.
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.
- 12d ago First seen · 78 lines · 22 tokens per session scan A b9c194fb9ba4
ultragoal is a skill published in the GitHub repository Yeachan-Heo/oh-my-codex (33,078 stars, last pushed yesterday), licensed MIT. It adds 22 tokens to every session and 1,087 once invoked, about $0.0001 per session on Opus 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…