speckit.spex-deep-review.run

speckit.spex-deep-review.run is a command for Claude Code from rhuss/cc-spex. It costs 38 tokens per session (12,519 once invoked), scanned A, original, Apache-2.0.

A multi-angle code-review command that asks five specialized reviewers to inspect correctness, design, security, production readiness, and test quality.

In plain words
What is it for?
Use it for a broad review after implementation or as part of a shipping workflow, with results saved in a review-findings document.
Why use it?
It combines different review perspectives, removes duplicate findings, and highlights issues by severity. Critical and important problems can trigger an automatic fix cycle.

Command for Claude Code

Written for Claude Code: a Claude Code command (commands/*.md). Also seen: mentions subagents; mentions Claude Code; mentions Codex.

Good fit Use it for a broad review after implementation or as part of a shipping workflow, with results saved in a review-findings document.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/rhuss/cc-spex/speckit.spex-deep-review.run
Install

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.

Clone the repo
git clone --depth 1 https://github.com/rhuss/cc-spex

Made for: Claude Code.

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 speckit.spex-deep-review.run

README.md
[![agentmods](https://agentmods.dev/badge/commands/rhuss/cc-spex/speckit.spex-deep-review.run/github.svg)](https://agentmods.dev/commands/rhuss/cc-spex/speckit.spex-deep-review.run)
Your own site
<a href="https://agentmods.dev/commands/rhuss/cc-spex/speckit.spex-deep-review.run"><img src="https://agentmods.dev/badge/commands/rhuss/cc-spex/speckit.spex-deep-review.run/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.

agentmods 80×15 button for speckit.spex-deep-review.run

Your own site · 80×15
<a href="https://agentmods.dev/commands/rhuss/cc-spex/speckit.spex-deep-review.run"><img src="https://agentmods.dev/badge/commands/rhuss/cc-spex/speckit.spex-deep-review.run.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 38 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 12,519 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.00038 $0.12519
Opus 5 $0.00019 $0.06259
Sonnet 5 $0.00008 $0.02504
Haiku 4.5 $0.00004 $0.01252

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

Security

Grade A, and why

speckit.spex-deep-review.run 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 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.

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.

specs/038-neutral-command-vocab/pre-rewrite-snapshot/spex-deep-review/commands/speckit.spex-deep-review.run.md · 1,179 lines

How it starts

The opening of the file, as written. The whole thing — 1,179 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Deep Review: Multi-Perspective Code Review

Overview

This command orchestrates a multi-perspective code review using five specialized review agents. Each agent analyzes code from a distinct angle (correctness, architecture, security, production readiness, test quality). Findings are merged, deduplicated, and classified by severity. Critical and Important findings trigger an autonomous fix loop (up to 3 rounds). Results are documented in review-findings.md.

This command is invoked by speckit-spex-gates-review-code when the deep-review extension is enabled, or via the after_implement hook.

Prerequisites

The caller (review-code or ship) may provide these values. When not provided, the deep-review command resolves them itself:

  1. Stage 1 result: spec compliance score (or null if no spec)
  2. Invocation context: superpowers or manual
  3. Hint text: optional focus area from user (or null)
  4. External tool settings: {coderabbit: true/false, copilot: true/false} (see resolution below)
  5. Spec path: path to spec.md (or null, see Spec Resolution below)
  6. Feature directory: path to the spec directory for artifact output

Spec Resolution

If the caller does not provide a spec path, attempt branch-based resolution:

.specify/scripts/bash/check-prerequisites.sh --json --paths-only 2>/dev/null

If this succeeds (outputs JSON with FEATURE_SPEC), use the resolved spec path and feature directory. If this fails (not on a feature branch, no matching spec directory), proceed without a spec (spec compliance checks will be skipped).

External Tool Settings Resolution

If external tool settings are provided by the caller, use them directly. If not (e.g., when invoked directly by speckit-spex-ship or manually), resolve from config:

# Read config defaults from deep-review extension config (all default to true if key is missing)
DEEP_REVIEW_CONFIG=".specify/extensions/spex-deep-review/deep-review-config.yml"
DEFAULT_CODERABBIT=$(yq -r '.external_tools.coderabbit // true' "$DEEP_REVIEW_CONFIG" 2>/dev/null)
DEFAULT_CODERABBIT=${DEFAULT_CODERABBIT:-true}
DEFAULT_COPILOT=$(yq -r '.external_tools.copilot // true' "$DEEP_REVIEW_CONFIG" 2>/dev/null)
DEFAULT_COPILOT=${DEFAULT_COPILOT:-true}

Read the full file on GitHub · 1,179 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. 10d ago First seen · 1,179 lines · 38 tokens per session scan A 1e069b8fed65

Subscribe to this mod's changes

speckit.spex-deep-review.run is a command published in the GitHub repository rhuss/cc-spex (117 stars, last pushed 22d ago), licensed Apache-2.0. It adds 38 tokens to every session and 12,519 once invoked, about $0.0002 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.