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.
git clone --depth 1 https://github.com/Fomo-Driven-Development/strategic-claude-baseWrote 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/fomo-driven-development/strategic-claude-base/codex-review)<a href="https://agentmods.dev/commands/fomo-driven-development/strategic-claude-base/codex-review"><img src="https://agentmods.dev/badge/commands/fomo-driven-development/strategic-claude-base/codex-review/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/commands/fomo-driven-development/strategic-claude-base/codex-review"><img src="https://agentmods.dev/badge/commands/fomo-driven-development/strategic-claude-base/codex-review.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00012 | $0.00266 |
| Opus 5.5 | $0.00005 | $0.00106 |
| Sonnet 5.5 | $0.00002 | $0.00053 |
| Haiku 4.5 | $0.00001 | $0.00027 |
Grade A, and why
codex-review 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 2mo 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.
What it actually says
You are tasked with reviewing code changes using the specialized codex-review agent. This command analyzes the most recent committed changes (or a specific commit if provided) and provides comprehensive code review feedback.
Commit reference (optional): $1
Process
-
Determine commit to review:
- If a commit reference is provided as $1, use that specific commit
- Otherwise, review the most recent commit (HEAD)
-
Launch codex-review agent:
- Use the Task tool with subagent_type "codex-review"
- Instruct the agent to analyze the specified commit changes
- The agent will provide prioritized findings, bug detection, and actionable recommendations
-
Present results:
- Display the comprehensive code review report from the codex-review agent
- Highlight any P0/P1 issues that require immediate attention
- Summarize key recommendations for the user
Command Implementation
This command provides a quick way to get professional code review feedback on recent changes without manually invoking the codex-review agent.
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.
- 2mo ago First seen · 33 lines · 12 tokens per session scan A 943374bc24f2
codex-review is a command published in the GitHub repository Fomo-Driven-Development/strategic-claude-base (2 stars, last pushed 11mo ago), licensed MIT. It adds 12 tokens to every session and 266 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-31.
Other commands, from other repositories
review-branch
Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.
refactor
Systematic code refactoring with smart scope detection.
spec-trace-requirements
You are verifying that implementation changes trace back to specification requirements.
init
Install the formatters this repository needs, with every command visible before it runs.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
boot
Start a new PromptKit prompt assembly session (alias for /bootstrap).