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/chrisblattman/claudeblattman/codexgit clone --depth 1 https://github.com/chrisblattman/claudeblattmanWrote 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/chrisblattman/claudeblattman/codex)<a href="https://agentmods.dev/commands/chrisblattman/claudeblattman/codex"><img src="https://agentmods.dev/badge/commands/chrisblattman/claudeblattman/codex.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.00673 |
| Opus 5 | $0.00012 | $0.00336 |
| Sonnet 5 | $0.00005 | $0.00135 |
| Haiku 4.5 | $0.00002 | $0.00067 |
Grade C, and why
codex scanned grade C with 1 finding 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 4d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
10. **Clean up.** Remove the temp directory (`rm -rf <rundir>`). Copies of this mod
1 near-identical copy found in the catalogue:
- gemini — 89% identical, 26 lines differ
How it starts
The opening of the file, as written. The whole thing — 39 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/codex — one-shot Codex query
Send the user's request to the Codex CLI and relay the answer. One question, one reply, read-only — Codex edits nothing.
Steps
-
Privacy check (required, every time). Sending this question transmits its content to another AI service. If the request or any pasted content includes confidential records, personal contact details, research-participant or human-subjects data, unpublished sensitive material, or anything the user wouldn't paste into a public website — do NOT send it. Explain why in one sentence and offer either a Claude-only answer or a redacted version the user approves first.
-
Explicit send confirmation (required, every time). If the privacy check passes, ask: "Send this prompt to Codex for a second opinion? (yes/no)" Proceed only if the user answers yes. If they answer no or do not answer clearly, stop and offer a Claude-only answer.
-
Check it's enabled. Read
~/.claude/starter-kit/engines.json. If the file is missing, unparseable, orcodex.availableis nottrue, print exactly this and stop:Running on Claude only — that's the normal setup and everything here works. (Have ChatGPT or Gemini? Run /kit-setup to plug them in.)
-
Re-check the binary. Run
command -v codex. Not found → print the same note and stop. -
Make a private workspace. Run
mktemp -donce and use the directory it prints (below:<rundir>) for both files. Never use predictable fixed paths like/tmp/codex-prompt.txt. -
Write the prompt to
<rundir>/prompt.txtwith the Write tool (NOT echo or a heredoc — shell quoting mangles multi-line prompts). Content: the user's request, verbatim. If empty, ask one line: "What should I ask Codex?" -
Run the wrapper (it picks the best available model and falls back automatically — never call
codex execdirectly):bash "${CLAUDE_PLUGIN_ROOT}/scripts/codex-run.sh" <rundir>/reply.txt < <rundir>/prompt.txtRun in the foreground and wait — it can take a minute or two.
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.
- 4d ago First seen · 39 lines · 24 tokens per session scan C b5ba74ea8c0a
codex is a command published in the GitHub repository chrisblattman/claudeblattman (454 stars, last pushed 2mo ago), licensed MIT. It adds 24 tokens to every session and 673 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
sync-config
Sync a scraping config's URLs against the live documentation site.
statusbar-doctor
Run cs doctor to diagnose why the status bar isn't showing what you expect.
statusbar
Show current status-bar config and list available styles + themes.
brief-compliance-check
Check a LaTeX coursework submission against the requirements in a supplied PDF assessment brief. Use when verifying format, required sections, word limits, or deliverables before submission. Not for general prose proofreading; use $proofread.
checkpoint
Save a compact continuation checkpoint so current work survives context compaction or a later session. Use when the active context is becoming long or work must pause without changing client or machine ownership. For an explicit cross-session/client transfer, use $handoff.
devils-advocate
Adversarially challenge research assumptions, mechanisms, and arguments in writing. Use when stress-testing a claim or design before committing to it. Not for an interactive oral drill or a full referee report; use $grill-me or a review agent.