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 agentmods add commands/anhnguyen0905/codex-mcp/codex-flowgit clone --depth 1 https://github.com/anhnguyen0905/codex-mcpWrote 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/commands/anhnguyen0905/codex-mcp/codex-flow)<a href="https://agentmods.dev/commands/anhnguyen0905/codex-mcp/codex-flow"><img src="https://agentmods.dev/badge/commands/anhnguyen0905/codex-mcp/codex-flow.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00024 | $0.13497 |
| Opus 5 | $0.00012 | $0.06749 |
| Sonnet 5 | $0.00005 | $0.02699 |
| Haiku 4.5 | $0.00002 | $0.01350 |
Grade A, and why
codex-flow 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 today.
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 — 622 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codex Flow — Plan with Claude, Execute with Codex, Review with Claude + Codex
Task: $ARGUMENTS
Follow these six phases (0–5) strictly. Do NOT write implementation code yourself — Codex does the implementation.
Each phase names plugin skills (codex-flow:*) to load via the Skill tool before starting the phase — they carry the detailed checklists. If a named skill is unavailable (command installed without the plugin), continue with the phase instructions below as written.
Phase 0 — Preflight (gate, do this FIRST)
Load skill first: codex-flow:preflight (health gate, resume check, workspace baseline) — it carries the detailed checklist for the steps below.
Call mcp__codex__codex_health before anything else:
- Tool call fails / server missing → the MCP server is not set up. Tell the user to follow the
install steps in the codex-mcp README (or run
node scripts/doctor.mjsin the codex-mcp repo), then offer the Executor fallback (section below): fix Codex and re-check, or continue with Claude as executor. Never continue silently. loggedIn: false→ tell the user to runcodex loginin their terminal (ChatGPT Plus/Pro/Team, or setOPENAI_API_KEY), then offer the Executor fallback: re-check after login, or continue with Claude as executor. Do not interview, plan, or execute anything until either a re-check showsloggedIn: trueor the user has explicitly chosen the fallback.loggedIn: true→ report the Codex version, keepexecutor: codex, and continue.
Exception: a failed health check or missing login does NOT block the analysis lane of the
Fast-path gate below — that lane needs no Codex session and no fallback decision. Tell the user
about the health failure, then proceed in the analysis lane; the small-change lane and the full
flow require either loggedIn: true or an explicit Executor-fallback choice.
Resume check — if .codex-flow/STATE.md exists, treat it as an interrupted run and offer
resume or restart, even when PLAN.md or TASKS.md has not been created yet. STATE.md is the
resume authority: skip only phases whose approvals STATE.md records, and enter the first unapproved
phase. Run node "${CLAUDE_PLUGIN_ROOT}/scripts/flow-state.mjs" check first: when it reports ONLY missing keys on a legacy file, add them with
set (currentTask -, taskStage idle, wave -) and continue; any other violation is surfaced
to the user before routing. Then route from STATE.md's recorded phase: for phase: execution, enter Phase 4 at the
first task not marked done — but first route by taskStage, regardless of currentTask
(currentTask names the task in sequential mode and is - with wave set in parallel mode):
reviewing → resume Phase 5 for that task; launching/executing → run the in-progress
reconciliation first; handoff → finish Phase 5 step 7 (or the wave's Step 3.8 handoff);
merge-conflict → surface it and STOP; idle → next pending task; for phase: review, resume Phase 5 completion work. When all tasks are
done but phase is not complete, resume Phase 5 for the final dual review, requirement ID-walk,
improvement gate, cost/report delivery gates, and completion write instead of concluding there is
nothing to do.
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.
- today Changed · +100 lines 6efde25735c0
- 4d ago First seen · 522 lines · 24 tokens per session scan A f63f197d6200
codex-flow is a command published in the GitHub repository anhnguyen0905/codex-mcp (3 stars, last pushed 2d ago), licensed MIT. It adds 24 tokens to every session and 13,497 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-31.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.