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-parity-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-parity-review)<a href="https://agentmods.dev/commands/severity1/claude-agent-sdk-go/tdd-parity-review"><img src="https://agentmods.dev/badge/commands/severity1/claude-agent-sdk-go/tdd-parity-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-parity-review"><img src="https://agentmods.dev/badge/commands/severity1/claude-agent-sdk-go/tdd-parity-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.00022 | $0.05186 |
| Opus 5 | $0.00011 | $0.02593 |
| Sonnet 5 | $0.00004 | $0.01037 |
| Haiku 4.5 | $0.00002 | $0.00519 |
Grade A, and why
tdd-parity-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 12d 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 — 272 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TDD Parity Review
REVIEW ONLY. This command reports findings. It never makes changes. After presenting results, stop and let the user decide what to fix.
Spawns a grumpy-gopher agent to review the current branch against one or more Python SDK parity items.
Two co-equal parity gates are checked. Both are mandatory. A violation of either is a blocker:
- Observable-behavior parity with Python SDK — wire format (JSON field names, constants, message shapes, CLI flags), public API surface (method/type/parameter names), and semantics (what each call does, what errors return, what fields populate).
- Idiomatic Go delivery — the shape of the code that delivers the parity contract: context-first,
fmt.Errorfwith%wwrapping, nil-safety, small focused interfaces, gofmt/golangci-lint clean, gocyclo under 15, channel-based concurrency, zero-value usability, no unnecessary exports.
Parity is the what. Idiomatic Go is the how. Neither is negotiable; neither is a polish step. Mirroring Python internals is not a goal — when a Go idiom and a Python internal shape conflict, choose the Go idiom and record the deliberate divergence. Beyond the two gates, the reviewer also checks regressions, example coverage, comment hygiene, and docs reconciliation.
Usage
/tdd-parity-review [python-pr-numbers]
Examples:
/tdd-parity-review— reviews all pending items on the current branch (auto-detected from tracker)/tdd-parity-review 506— reviews Python PR #506 specifically/tdd-parity-review 506 516— reviews both PRs
Step 1: Gather Context
Run these in parallel:
git diff main...HEAD --stat
git log main..HEAD --oneline
git diff main...HEAD -- <substantive Go files, exclude CLAUDE.md/auto-memory>
Read docs/tracking/README.md to get the spec for each target PR: expected types, field names, wire format, JSON tags, method signatures.
If $ARGUMENTS is empty, infer target PRs from the tracker: find items whose Go Status is pending and whose description matches files changed on this branch.
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.
- 12d ago First seen · 272 lines · 22 tokens per session scan A 189650b5bde6
tdd-parity-review is a command published in the GitHub repository severity1/claude-agent-sdk-go (170 stars, last pushed 3mo ago), licensed MIT. It adds 22 tokens to every session and 5,186 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
go-review
Go code review for idiomatic patterns.
go-review
Comprehensive Go code review for idiomatic patterns, concurrency safety, error handling, and security. Invokes the go-reviewer agent.
go-test
Go TDD workflow with table-driven tests.
rust-review
Rust code review for ownership, safety, and idiomatic patterns.
go-build
Fix Go build and vet errors.
review-pr-staging
Staging review mode — comprehensive review of staging branch before deploy to main.