Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
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.
[](https://agentmods.dev/commands/severity1/claude-agent-sdk-go/tdd)<a href="https://agentmods.dev/commands/severity1/claude-agent-sdk-go/tdd"><img src="https://agentmods.dev/badge/commands/severity1/claude-agent-sdk-go/tdd.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.00013 | $0.05455 |
| Opus 5 | $0.00006 | $0.02728 |
| Sonnet 5 | $0.00003 | $0.01091 |
| Haiku 4.5 | $0.00001 | $0.00545 |
Grade A, and why
tdd scanned grade A with 1 finding 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 6d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- **Fetch official documentation** using `curl -s https://platform.claude.com/docs/en/agent-sdk/python.md` for public API signatures if helpful How it starts
The opening of the file, as written. The whole thing — 454 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TDD Development Cycle
Execute complete TDD workflow for GitHub issue #$ARGUMENTS with built-in quality gates and Python SDK parity checks.
Phase 1: Pre-flight Checks
Verify the development environment is ready:
- Check working directory status - Ensure no uncommitted changes exist
- Verify current branch - Should be on
mainbranch - Pull latest changes - Run
git pullto sync with remote - Check for existing PRs - Search for open PRs linked to issue #$ARGUMENTS to avoid duplicate work
- Verify Go environment - Run
go versionand ensure toolchain is available - Sync Python SDK - Run
git -C ../claude-agent-sdk-python pull origin mainto ensure local Python SDK reference is current - Check for blocking dependencies - Read issue body and look for "Depends on" or "Blocked by" sections
STOP and report to user if any check fails - Don't proceed until issues are resolved.
Phase 2: Issue Validation
Retrieve and analyze issue #$ARGUMENTS:
- Fetch issue details - Get title, body, labels, milestone, state via
gh issue view - Read all comments - Check for additional context or decisions made
- Validate issue completeness - Check if issue contains:
- Summary or description of the feature/fix
- Proposed Implementation section (most issues have this)
- Files to Modify section
- Example Usage (if applicable)
If incomplete: Report gaps to user and ask if should proceed anyway. If complete: Display issue summary and continue.
Phase 3: Discovery & Planning
Enter plan mode for this entire phase. Call EnterPlanMode at the start of Phase 3 so all discovery, design decisions, and parity tradeoffs are captured as a plan the user approves before any code is written. The phase ends with ExitPlanMode at the Critical Checkpoint below. If already in plan mode, EnterPlanMode is a no-op — proceed.
Design Principle: Two Co-Equal Parity Gates
This work passes through two co-equal mandatory gates. Both must pass. Neither compensates for the other:
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.
- 6d ago First seen · 454 lines · 13 tokens per session scan A 3b028f3b32f2
tdd is a command published in the GitHub repository severity1/claude-agent-sdk-go (170 stars, last pushed 2mo ago), licensed MIT. It adds 13 tokens to every session and 5,455 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
implement
Execute tasks from a track's implementation plan following TDD workflow.
implement-feature
Implement an approved feature plan with fresh-context slices, TDD, evidence, and PR-ready output.
run
Implement SPEC requirements using DDD/TDD methodology.
fd-execute
Implement plan.md with the TDD pipeline — parallel worktree guard from affect.md, wave-based execution, checkpoint after each wave.
fix-bug
Systematically reproduce, isolate, fix, test, and document a bug.
dev-tdd
Implements a feature by following the TDD (Test-Driven Development) cycle.