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/rhuss/cc-spexWrote 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/rhuss/cc-spex/speckit.spex-gates.review-code)<a href="https://agentmods.dev/commands/rhuss/cc-spex/speckit.spex-gates.review-code"><img src="https://agentmods.dev/badge/commands/rhuss/cc-spex/speckit.spex-gates.review-code.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.00011 | $0.03213 |
| Opus 5 | $0.00005 | $0.01606 |
| Sonnet 5 | $0.00002 | $0.00643 |
| Haiku 4.5 | $0.00001 | $0.00321 |
Grade A, and why
speckit.spex-gates.review-code 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 8d 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 — 423 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Review Against Specification
Ship Pipeline Guard
If .specify/.spex-state exists and its status is running, this command is part of an autonomous pipeline. Check the ask field:
- If
askis"smart"or"never": suppress all user prompts (do NOT prompt the user interactively), complete the review autonomously, and return immediately so the pipeline can advance. - If
askis"always": prompt the user as normal.
if [ -f ".specify/.spex-state" ]; then
STATUS=$(jq -r '.status // empty' .specify/.spex-state 2>/dev/null)
ASK=$(jq -r '.ask // "always"' .specify/.spex-state 2>/dev/null)
if [ "$STATUS" = "running" ] && [ "$ASK" != "always" ]; then
echo "AUTONOMOUS_MODE=true"
else
echo "AUTONOMOUS_MODE=false"
fi
else
echo "AUTONOMOUS_MODE=false"
fi
In autonomous mode: do NOT output a completion summary, do NOT ask "Shall I proceed?", do NOT suggest next steps. Complete the review and return.
Flow Status Update (before review starts)
If review-code is running, implementation is by definition done. Mark it immediately so the status line shows impl ✓ during the review:
FLOW_STATE=".specify/extensions/spex-gates/scripts/spex-flow-state.sh" && [ -x "$FLOW_STATE" ] && "$FLOW_STATE" implemented && "$FLOW_STATE" running review-code
IMPORTANT: Deep Review Extension Check
Before starting any review work, check if the spex-deep-review extension is enabled:
# Check via extensions registry
jq -r '.extensions["spex-deep-review"].enabled // false' .specify/extensions/.registry 2>/dev/null
If deep review is enabled, this command MUST invoke speckit.spex-deep-review.run after spec compliance passes (>= 95%). Do NOT produce only a basic compliance review when deep-review is active. The deep review dispatches 5 specialized agents, runs a fix loop, and generates a Deep Review Report. See step 9a below for details.
Overview
Review code implementation against specification to ensure compliance.
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.
- 8d ago First seen · 423 lines · 11 tokens per session scan A 1e341b1d9e93
speckit.spex-gates.review-code is a command published in the GitHub repository rhuss/cc-spex (115 stars, last pushed 19d ago), licensed Apache-2.0. It adds 11 tokens to every session and 3,213 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-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.
review-sdk-app
Review and validate a Claude Agent SDK application against best practices.
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.