Borrowing it
Nothing to install: this file belongs to severity1/claude-agent-sdk-go. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/severity1/claude-agent-sdk-go/main/.claude/commands/tdd-review.mdgit clone --depth 1 https://github.com/severity1/claude-agent-sdk-goWrote 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/severity1/claude-agent-sdk-go/tdd-review)<a href="https://agentmods.dev/commands/severity1/claude-agent-sdk-go/tdd-review"><img src="https://agentmods.dev/badge/commands/severity1/claude-agent-sdk-go/tdd-review/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.
<a href="https://agentmods.dev/commands/severity1/claude-agent-sdk-go/tdd-review"><img src="https://agentmods.dev/badge/commands/severity1/claude-agent-sdk-go/tdd-review.svg" alt="Reviewed on agentmods" width="80" 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.00013 | $0.02989 |
| Opus 5.5 | $0.00005 | $0.01196 |
| Sonnet 5.5 | $0.00003 | $0.00598 |
| Haiku 4.5 | $0.00001 | $0.00299 |
Grade A, and why
tdd-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 1mo 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 — 313 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TDD Code Review (Team-Based)
Comprehensive code review for the Go SDK. Orchestrates multiple reviewers to analyze Go idioms, error handling, type design, test coverage, and Python SDK parity.
Prerequisite: Load Deferred Tools
Team and task orchestration tools (TeamCreate, TeamDelete, TaskCreate, TaskUpdate, TaskList, TaskGet, SendMessage, AskUserQuestion) are deferred in this harness. Before entering Phase 1, load them via:
ToolSearch(query="select:TeamCreate,TeamDelete,TaskCreate,TaskUpdate,TaskList,TaskGet,SendMessage,AskUserQuestion", max_results=8)
Skip this for quick-mode runs.
Quick Mode Exception
For focused reviews, use a single bare Agent call (model: "sonnet") with NO team:
--quick— Onlygrumpy-gopher--errors— Onlypr-review-toolkit:silent-failure-hunter--types— Onlypr-review-toolkit:type-design-analyzer--tests— Onlypr-review-toolkit:pr-test-analyzer--parity—grumpy-gopherwith explicit instructions to cross-referencedocs/tracking/README.mdand../claude-agent-sdk-python/for Python SDK divergence
If $ARGUMENTS contains any of these flags, extract the flag, launch the single appropriate agent with the file list, present results, and stop. Do not create a team, do not load team tools.
Review Scope Detection
Determine what code to review:
- User-specified files: If user provided specific files or packages after the flag/arguments, use those.
- Unstaged changes:
git diff --name-only - Staged changes:
git diff --staged --name-only - Default: Current package (
./...)
git diff --name-only
git diff --staged --name-only
Store the file list. If no files found, report and exit cleanly (no team created).
Reviewer Selection
Based on files identified, select reviewers:
| File Pattern | Reviewer |
|---|---|
internal/control/* |
grumpy-gopher, pr-review-toolkit:silent-failure-hunter |
internal/parser/* |
grumpy-gopher, pr-review-toolkit:silent-failure-hunter |
internal/subprocess/* |
grumpy-gopher, pr-review-toolkit:silent-failure-hunter |
internal/cli/* |
grumpy-gopher |
internal/shared/* |
grumpy-gopher, pr-review-toolkit:type-design-analyzer |
Root *.go (public API: client.go, query.go, options.go, errors.go, transport.go) |
grumpy-gopher, pr-review-toolkit:type-design-analyzer |
*_test.go, *_bench_test.go |
pr-review-toolkit:pr-test-analyzer |
examples/* |
grumpy-gopher (informational only) |
| Any Go file | grumpy-gopher, pr-review-toolkit:silent-failure-hunter (always) |
| Scope spans 2+ packages | Add pr-review-toolkit:code-reviewer |
| Diff adds large docstrings/comment blocks | Add pr-review-toolkit:comment-analyzer |
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.
- 1mo ago First seen · 313 lines · 13 tokens per session scan A 0f59cce98ce4
tdd-review is a command published in the GitHub repository severity1/claude-agent-sdk-go (176 stars, last pushed 23d ago), licensed MIT. It adds 13 tokens to every session and 2,989 once invoked, about $0.0001 per session on Opus 5.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
full-review
Orchestrate comprehensive multi-dimensional code review using specialized review agents across architecture, security, performance, testing, and best practices.
implement
Execute tasks from a track's implementation plan following TDD workflow.
dev-tdd
Implements a feature by following the TDD (Test-Driven Development) cycle.
work-flow-bugfix
Complete workflow to fix a bug, from diagnosis to deployment.
work-flow-feature
Complete workflow for developing a new feature, from exploration to merge.
work-batch
Autonomous and sequential execution of user stories from a PRD file (JSON or Markdown).