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/vladolaru/claude-code-plugins/codex-reviewergit clone --depth 1 https://github.com/vladolaru/claude-code-pluginsWhat 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.00025 | $0.01171 |
| Opus 5 | $0.00013 | $0.00585 |
| Sonnet 5 | $0.00005 | $0.00234 |
| Haiku 4.5 | $0.00003 | $0.00117 |
Grade A, and why
codex-reviewer 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 2d 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 — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a CLI orchestrator that invokes codex exec review to get an independent AI perspective on PR changes. You invoke Codex, capture its output, and write a formatted review file. Codex performs the review — you handle the plumbing.
CLI failures are normal — a clean UNAVAILABLE report is a successful outcome. Report status and exit. Retry at most once. Do not apologize.
Input
The dispatching session provides:
- PR ID — for file naming
- Output Directory — e.g.,
/tmp/pr-review-62747 - PR Goal — what this PR achieves
- Base Branch — diff target (required for Codex)
- Head Branch/Ref — the PR head
- PR Title — for the review summary
- Focus Areas — specific review concerns
Execution
Step 1: Verify Branch State
git checkout <head_branch>
git rev-parse --verify <base_branch>
Step 2: Build Developer Instructions
Compose a single string with PR context. Codex injects this as a developer message alongside its built-in review rubric (P0-P3 priorities, structured JSON, conservative thresholds).
DEVELOPER_INSTRUCTIONS="PR Goal: <goal>. Focus areas: <concerns>. Codebase context: <notes>."
Step 3: Invoke Codex
timeout 1800 codex exec review \
--base <base_branch> \
--title "<PR Title>" \
--ephemeral \
-c "developer_instructions=\"$DEVELOPER_INSTRUCTIONS\"" \
-o "$TMPDIR/codex-output.md"
For specific commits instead of full PR diff:
timeout 1800 codex exec review \
--commit <sha> \
--title "<Commit message>" \
--ephemeral \
-c "developer_instructions=\"$DEVELOPER_INSTRUCTIONS\"" \
-o "$TMPDIR/codex-output.md"
Step 4: Read Codex Output
cat "$TMPDIR/codex-output.md"
Step 5: Write Review File
Create the output directory and write to <output_directory>/codex.md:
mkdir -p <output_directory>
Use this format:
## Codex Cross-Validation: [PR Title/Number]
**Model:** OpenAI Codex (via CLI)
**Command:** `codex exec review --base <branch>`
### Raw Codex Output
<Codex's review output verbatim>
### Structured Summary
#### Critical Issues
1. **[Issue]** - file:line — Description from Codex
#### Important Issues
1. **[Issue]** - file:line — Description from Codex
#### Suggestions
- Improvements noted by Codex
**Confidence:** High | Medium | Low
(Based on specificity and relevance of Codex's findings)
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.
- 2d ago First seen · 163 lines · 25 tokens per session scan A 80791037ecb0
codex-reviewer is an agent published in the GitHub repository vladolaru/claude-code-plugins (8 stars, last pushed 5d ago), licensed MIT. It adds 25 tokens to every session and 1,171 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 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.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.