Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add v11g/codex-review-cc/plugin install codexWrote 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/v11g/codex-review-cc/spec-review)<a href="https://agentmods.dev/commands/v11g/codex-review-cc/spec-review"><img src="https://agentmods.dev/badge/commands/v11g/codex-review-cc/spec-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.1 | $0.00000 | $0.03151 |
| Opus 5 | $0.00000 | $0.01576 |
| Sonnet 5 | $0.00000 | $0.00630 |
| Haiku 4.5 | $0.00000 | $0.00315 |
Grade A, and why
spec-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 7d 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 — 218 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/codex:spec-review — Adversarial Codex review of a spec or plan
Summon OpenAI Codex to adversarially review the latest (or named) superpowers spec or plan, then debate until Codex approves. Codex is the hard gate.
$ARGUMENTS (optional): a target word spec or plan, and/or a name keyword.
Examples: /codex:spec-review, /codex:spec-review plan, /codex:spec-review spec evals-dataset.
Every shell block below runs under bash.
codex-lib.shand its helpers use bash arrays and abort under zsh/sh, so each block is wrapped inbash <<'CODEX_SH' … CODEX_SH— it runs under bash even when your default shell is zsh. And because each block runs in a fresh shell (sourced functions and vars do not persist between calls), every block re-resolves and re-sources the lib, then hands values to the next block through a per-repo state file (sr_state_file/sr_state_save/sr_state_load). The shared preamble — resolveLIB, source it,sr_state_load "$STATE"— opens every block.
1. Preflight
bash <<'CODEX_SH'
# Resolve the plugin's lib. Order: installed plugin root, project-local checkout,
# a manual ~/.claude install, then the plugin cache (the unset-env fallback).
LIB=""
for d in "${CLAUDE_PLUGIN_ROOT:-}" ".claude/commands/codex" "${CLAUDE_HOME:-$HOME/.claude}/commands/codex" $(printf '%s\n' "${CLAUDE_HOME:-$HOME/.claude}"/plugins/cache/*/codex/* 2>/dev/null | sort -Vr); do
[ -n "$d" ] && [ -f "$d/codex-lib.sh" ] && { LIB="$d/codex-lib.sh"; break; }
done
[ -n "$LIB" ] || { echo "codex-lib.sh missing — install the plugin or run install.sh"; exit 1; }
. "$LIB" || { echo "codex-lib.sh failed to source"; exit 1; }
command -v codex >/dev/null 2>&1 || { echo "codex CLI not on PATH"; exit 1; }
have="$(codex --version 2>/dev/null | grep -oE '[0-9]+\.[0-9]+\.[0-9]+' | head -1)"
sr_version_ge "${have:-0.0.0}" 0.140.0 || { echo "codex >= 0.140.0 required (have ${have:-none})"; exit 1; }
# Fresh-shell handoff: start a clean state file and persist LIB for later blocks.
STATE="$(sr_state_file spec-review)"; : > "$STATE"; sr_state_save "$STATE" LIB
echo "Preflight OK (codex ${have:-?}); state $STATE"
CODEX_SH
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.
- 7d ago First seen · 218 lines · 0 tokens per session scan A 7bb1b6eff6ad
spec-review is a command published in the GitHub repository v11g/codex-review-cc (6 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,151 tokens. 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
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.