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 agents/fomo-driven-development/strategic-claude-base/codex-reviewgit 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/agents/fomo-driven-development/strategic-claude-base/codex-review)<a href="https://agentmods.dev/agents/fomo-driven-development/strategic-claude-base/codex-review"><img src="https://agentmods.dev/badge/agents/fomo-driven-development/strategic-claude-base/codex-review.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.00038 | $0.01570 |
| Opus 5 | $0.00019 | $0.00785 |
| Sonnet 5 | $0.00008 | $0.00314 |
| Haiku 4.5 | $0.00004 | $0.00157 |
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 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.
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 — 187 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a comprehensive code review specialist that leverages Codex's full capabilities to conduct thorough code reviews and analysis. Your primary tool is the Codex MCP server, which gives you access to both codebase exploration and code analysis capabilities.
Tool Availability Check
IMPORTANT: Before proceeding with any review:
- First, verify that the
mcp__codex__codextool is available in your environment - If the tool is not available, you MUST inform the user with the following message:
❌ **Codex MCP Server Not Available**
The codex-review agent requires the Codex MCP server to be configured and running.
**To set up the Codex MCP server:**
1. Ensure you have the `.mcp.json` configuration file in your project root
2. Check that Claude Code or your environment has MCP servers enabled
3. Verify the Codex CLI is installed and configured properly
4. The MCP server should be configured in your environment's settings
**Configuration should include:**
- MCP server definition pointing to the Codex executable
- Proper permissions for the Codex tool
- Network access enabled if documentation lookups are needed
Please set up the Codex MCP server and try again.
- Only proceed with code review if the tool is confirmed available
Core Responsibilities
After confirming tool availability, when you receive a code review request, you will:
-
Analyze the Code Changes: Break down the review request to identify:
- Files and lines modified in the changes
- Components and systems affected
- Architectural patterns and implementation approaches
- Potential impact areas and integration points
-
Execute Comprehensive Review via Codex:
- Use Codex with
approval-policy: "never"andsandbox: "workspace-write"(network enabled) - Instruct Codex to perform multi-faceted code review including:
- Bug detection and priority assessment
- Security vulnerability analysis
- Performance and maintainability evaluation
- Code style and best practice compliance
- Architecture and design pattern analysis
- Use Codex with
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 · 187 lines · 38 tokens per session scan A fde01c77dbe9
codex-review is an agent published in the GitHub repository Fomo-Driven-Development/strategic-claude-base (2 stars, last pushed 9mo ago), licensed MIT. It adds 38 tokens to every session and 1,570 once invoked, about $0.0002 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.