spec-review

spec-review is a command for Claude Code, Codex from v11g/codex-review-cc. It costs 0 tokens per session (3,151 once invoked), scanned A, original, MIT.

A command that asks OpenAI Codex to challenge and review a software specification or plan until it approves it. A specification describes what should be built; a plan describes how to build it.

In plain words
What is it for?
Use it to review the latest or a named spec or plan, with optional words such as “spec” or “plan” and a name keyword to select the target.
Why use it?
It adds a strict review step for finding gaps or weak decisions before implementation begins.

Command for Claude CodeCodex

Written for Claude Code and Codex: ${CLAUDE_PLUGIN_ROOT variable, but also runs codex exec. Also seen: reads .claude/ paths; mentions CLAUDE.md; mentions subagents.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the codex plugin — 2 commands shipped together

Good fit Use it to review the latest or a named spec or plan, with optional words such as “spec” or “plan” and a name keyword to select the target.

Compare 6 commands from other repositories ↓
Install

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.

Claude Code
/plugin marketplace add v11g/codex-review-cc
Claude Code
/plugin install codex

Made for: Claude Code, Codex.

Or install codex, the plugin that ships this one along with the rest of its 2 commands.

Wrote 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.

agentmods badge for spec-review

README.md
[![agentmods](https://agentmods.dev/badge/commands/v11g/codex-review-cc/spec-review.svg)](https://agentmods.dev/commands/v11g/codex-review-cc/spec-review)
Your own site
<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>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,151 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 7d ago against content hash 7bb1b6eff6ad, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

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.

commands/spec-review.md · 218 lines

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.sh and its helpers use bash arrays and abort under zsh/sh, so each block is wrapped in bash <<'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 — resolve LIB, 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

Read the full file on GitHub · 218 lines

Changes

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.

  1. 7d ago First seen · 218 lines · 0 tokens per session scan A 7bb1b6eff6ad

Subscribe to this mod's changes

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.