debug-toolbar: Command for Claude Code

.claude/commands/review.md

review is a command for Claude Code from JacobCoffee/debug-toolbar. It costs 6 tokens per session (924 once invoked), scanned A, original, MIT.

A code-review workflow that checks changed files against project requirements and quality rules. It runs tests, linting, type checks, formatting checks, coverage checks, and scans for unwanted coding patterns.

In plain words
What is it for?
Use it to review an implementation, verify project quality gates, find anti-patterns, and record new project patterns or needed documentation updates.
Why use it?
It turns review into a repeatable quality check instead of relying only on manual inspection. It helps catch failing tests, type errors, formatting problems, low coverage, and inconsistencies before changes are accepted.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: mentions CLAUDE.md.

This is JacobCoffee/debug-toolbar's own configuration. It tells Claude Code how to work on debug-toolbar itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything debug-toolbar configures →

Reuse

Borrowing it

Nothing to install: this file belongs to JacobCoffee/debug-toolbar. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/JacobCoffee/debug-toolbar/main/.claude/commands/review.md
Clone the repo
git clone --depth 1 https://github.com/JacobCoffee/debug-toolbar

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 review

README.md
[![agentmods](https://agentmods.dev/badge/commands/jacobcoffee/debug-toolbar/review.svg)](https://agentmods.dev/commands/jacobcoffee/debug-toolbar/review)
Your own site
<a href="https://agentmods.dev/commands/jacobcoffee/debug-toolbar/review"><img src="https://agentmods.dev/badge/commands/jacobcoffee/debug-toolbar/review.svg" alt="Measured on agentmods" height="20"></a>
Per session 6 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 924 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.00006 $0.00924
Opus 5 $0.00003 $0.00462
Sonnet 5 $0.00001 $0.00185
Haiku 4.5 $0.00001 $0.00092

Measured 2d ago against content hash 653386307cf9, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

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 2d 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.

.claude/commands/review.md · 186 lines

How it starts

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

Review Workflow

You are reviewing the implementation of: $ARGUMENTS

Pre-Review Checklist

  1. Load PRD from specs/active/{slug}/prd.md
  2. Load quality gates from specs/guides/quality-gates.yaml
  3. Review all modified files
  4. Check test coverage

Critical Rules

  1. ALL GATES MUST PASS - No exceptions
  2. PATTERN EXTRACTION - Capture new patterns
  3. ANTI-PATTERN SCAN - Check for violations
  4. DOCUMENTATION UPDATE - Update CLAUDE.md if needed

Phase 1: Quality Gate Verification

Run all quality gates:

make test          # All tests pass
make lint          # Zero linting errors
make type-check    # Type checking passes
make fmt-check     # Formatting correct

Verify coverage:

make test-cov
# Check: Modified modules >= 90%

Output: "✓ Phase 1 complete - All quality gates passed"


Phase 2: Anti-Pattern Scan

Check for anti-patterns:

  1. Optional[T] - Should use T | None

    grep -r "Optional\[" src/ tests/
    
  2. Missing future annotations

    for f in $(find src/ -name "*.py"); do
      head -5 "$f" | grep -q "from __future__ import annotations" || echo "Missing: $f"
    done
    
  3. Type ignore without code

    grep -r "# type: ignore$" src/ tests/
    
  4. Context var cleanup missing

    grep -A5 "@pytest.mark.asyncio" tests/ | grep -v "set_request_context(None)"
    

Fix any violations before proceeding.

Output: "✓ Phase 2 complete - No anti-patterns found"


Phase 3: Pattern Extraction

Review new patterns from implementation:

  1. Read specs/active/{slug}/tmp/new-patterns.md
  2. Identify reusable patterns
  3. Extract to specs/guides/patterns/

For each new pattern:

# Pattern: {Name}

## Context
When to use this pattern.

## Implementation
```python
# Code example

Usage

How to apply this pattern.


**Output**: "✓ Phase 3 complete - Patterns extracted"

---

Read the full file on GitHub · 186 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. 2d ago First seen · 186 lines · 6 tokens per session scan A 653386307cf9

Subscribe to this mod's changes

review is a command published in the GitHub repository JacobCoffee/debug-toolbar (7 stars, last pushed 5mo ago), licensed MIT. It adds 6 tokens to every session and 924 once invoked, about $0.0000 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-09-04.