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/adamjgmiller/adamsreviewWrote 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/adamjgmiller/adamsreview/codex-review)<a href="https://agentmods.dev/commands/adamjgmiller/adamsreview/codex-review"><img src="https://agentmods.dev/badge/commands/adamjgmiller/adamsreview/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/adamjgmiller/adamsreview/codex-review"><img src="https://agentmods.dev/badge/commands/adamjgmiller/adamsreview/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.00037 | $0.03487 |
| Opus 5 | $0.00018 | $0.01743 |
| Sonnet 5 | $0.00007 | $0.00697 |
| Haiku 4.5 | $0.00004 | $0.00349 |
Grade B, and why
codex-review scanned grade B 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 10d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
CODEX_COMPANION="$(find ~/.claude/plugins -type f -name codex-companion.mjs -path '*codex*' 2>/dev/null | head -1)" How it starts
The opening of the file, as written. The whole thing — 270 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Flags (optional):
--effort <level>controls Codex reasoning depth (low,medium,high,xhigh). Defaulthigh. Higher = deeper analysis but longer wall-clock and higher cost.--fullforcestrivial_mode=falsefor this run (overrides the doc/config-PR early-exit). Same semantics as:review --full.
Note: this command has no --ensemble flag — it is purpose-built
for Codex-only review. If you want internal Claude lenses pooled with
the Codex CLI + a PR bot-comment scrape, run /adamsreview:review --ensemble instead.
Read fragments/_prelude-shared.md before proceeding — it lists
rules that apply to every phase below (sub-agent return handling,
helper-script error-as-prompt).
Execution overview
This command orchestrates the same phases as /adamsreview:review
(Phases 0–6 plus Phase 5.5 auto-fix-hint generation), swapping the
Claude sub-agent dispatches for Codex jobs (via the
codex-companion.mjs plugin's task --background primitive) at:
- Phase 1 detection — 7 parallel Codex lenses (L1–L7) instead of
Claude
Agentblocks. - Phase 4a deep validation — one parallel Codex job per surviving finding instead of one Opus sub-agent per finding.
- Phase 4b light confirmation — chunked-batch Codex (≤25 candidates per chunk) instead of chunked-batch Sonnet.
- Phase 5 cross-cutting — one Codex pass instead of one Opus pass.
Claude sub-agents (Sonnet) are still used for the "shape-fixer" /
normalizer / dedup / scoring work where structured output matters
more than reasoning depth — all of these phases execute the SAME
fragments as :review:
- Phase 0 preflight —
fragments/00-preflight.mdverbatim. - Phase 2 dedup —
fragments/03-dedup.mdverbatim. - Phase 3 scoring gate —
fragments/04-scoring-gate.mdverbatim. - Phase 6 finalize —
fragments/07-finalize.mdverbatim.
Each phase below is defined in a fragment under fragments/NN-<name>.md.
At each phase boundary, read the named fragment with the Read tool
and execute the instructions inside before proceeding to the next phase.
Before you start, build a TaskList that mirrors the phases below
(one task per phase, plus one for argument parsing). Mark each
in_progress when you start it and completed when you finish.
If a phase genuinely cannot run, mark the task completed with a
one-line trace.md note and move on. Phase 6 (finalize) runs
unconditionally — a partial review is still worth rendering and
publishing so the user can inspect what did succeed.
Codex job failures (non-zero exit, malformed output, sentinel timeout)
are handled per the adaptive retry-with-orchestrator-judgment
policy: retry up to 3 times with the same prompt; on persistent
failure, drop the affected unit (lens / finding / chunk) and escalate
to the user via AskUserQuestion ("L2 failed; continue with 6 lenses
or abort?"). Log every drop to trace.md with tag
phase_<N>_codex_dropped:<unit_id>. This policy is restated where it
applies in each Codex-using fragment.
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.
- 10d ago First seen · 270 lines · 37 tokens per session scan B 1cea10b0b2ed
codex-review is a command published in the GitHub repository adamjgmiller/adamsreview (243 stars, last pushed 3mo ago), licensed MIT. It adds 37 tokens to every session and 3,487 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
sdd-init
Initialize SDD context — detects project stack and bootstraps persistence backend.
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.
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 }}.
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.
argos
A command for checking whether an implementation matches its design deliverables. Its Korean description compares the work to the design as part of a completion inspection.