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 commands/zts0hg/codexspec/review-specgit clone --depth 1 https://github.com/Zts0hg/codexspecWrote 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/zts0hg/codexspec/review-spec)<a href="https://agentmods.dev/commands/zts0hg/codexspec/review-spec"><img src="https://agentmods.dev/badge/commands/zts0hg/codexspec/review-spec.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.00015 | $0.01051 |
| Opus 5 | $0.00008 | $0.00526 |
| Sonnet 5 | $0.00003 | $0.00210 |
| Haiku 4.5 | $0.00002 | $0.00105 |
Grade A, and why
review-spec 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Specification Reviewer
Language Preference
Read .codexspec/config.yml. Two independent language controls apply (each falls back to language.output, then English):
- Interaction language (
language.interaction): language for all conversation with the user — questions, explanations, status messages, andcodexspecCLI terminal output. - Document language (
language.document): language for generated artifact files (requirements/spec/plan/tasks).
Converse in the interaction language and author artifacts in the document language. Apply the project's translation standard to both: translate by meaning (not word-for-word), keep English for terms with no good native equivalent, and write as if originally in that language.
User Input
$ARGUMENTS
Review Authority
Resolve the feature by explicit path, then current branch. Never silently select the latest feature.
Read requirements.md, spec.md, and the constitution. If requirements.md is absent, enter legacy compatibility mode: use spec.md as temporary authority and state that fidelity to the original discussion cannot be verified.
Authority order:
- Confirmed requirements and decisions
- The specification being reviewed
- Constitution and verified repository facts
- Applicable best practices
Review Passes
1. Fidelity
- Map every confirmed
NEED,CON,DEC, andOUTentry to the specification. - Detect omissions, semantic changes, scope expansion, promoted open questions, and ignored superseding decisions.
- Verify every
REQ/NFRhas validSources:.
2. Intrinsic Quality
Report only defects that can affect the user goal or technical planning:
- Contradictions
- Multiple materially different interpretations
- Untestable required behavior
- Missing expected behavior for relevant failure or boundary cases
- Impossible or unverifiable requirements
Do not require a section, metric, persona format, or example merely because a template contains it.
3. Advisories
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 · 135 lines · 15 tokens per session scan A e094ae257094
review-spec is a command published in the GitHub repository Zts0hg/codexspec (5 stars, last pushed 2d ago), licensed MIT. It adds 15 tokens to every session and 1,051 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 commands, from other repositories
review-agentready
AgentReady-specific code review with attribute mapping and score impact analysis.
speckit.specify
Create or update the feature specification from a natural language feature description.
speckit.checklist
Generate a custom checklist for the current feature based on user requirements.
speckit.implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
speckit.tasks
Generate an actionable, dependency-ordered tasks.md for the feature based on available design artifacts.
speckit.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.