Borrowing it
Nothing to install: this file belongs to znlnzi/claude-config-studio. 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/znlnzi/claude-config-studio/main/.claude/commands/tdd.mdgit clone --depth 1 https://github.com/znlnzi/claude-config-studioWrote 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/znlnzi/claude-config-studio/tdd)<a href="https://agentmods.dev/commands/znlnzi/claude-config-studio/tdd"><img src="https://agentmods.dev/badge/commands/znlnzi/claude-config-studio/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.00014 | $0.00318 |
| Opus 5 | $0.00007 | $0.00159 |
| Sonnet 5 | $0.00003 | $0.00064 |
| Haiku 4.5 | $0.00001 | $0.00032 |
Grade A, and why
tdd 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 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.
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.
What it actually says
/tdd - 测试驱动开发
强制执行 RED → GREEN → REFACTOR 循环。
工作流
1. 接口定义
- 定义输入/输出类型
- 明确函数签名
- 确定边界条件
2. 编写测试 (RED)
在编写任何实现之前：
- 编写覆盖正常路径的测试
- 编写覆盖边缘情况的测试
- 编写覆盖错误场景的测试
- 运行测试，确认全部失败
3. 最小实现 (GREEN)
- 编写满足测试的最小代码
- 不要过度设计
- 运行测试，确认全部通过
4. 重构 (REFACTOR)
- 在测试保护下改善代码质量
- 消除重复
- 提升可读性
- 运行测试，确认仍然通过
5. 覆盖率验证
- 检查覆盖率是否达到 80%
- 补充遗漏的测试场景
适用场景
- 新功能和函数
- Bug 修复（先写复现测试）
- 重构工作
- 关键业务逻辑
关键规则
测试必须在实现之前编写。 关键领域（认证、支付、安全）需要 100% 覆盖率。
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 · 48 lines · 14 tokens per session scan A 47b8a18dc641
tdd is a command published in the GitHub repository znlnzi/claude-config-studio (0 stars, last pushed 6mo ago), licensed MIT. It adds 14 tokens to every session and 318 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-31.
Other commands, from other repositories
workflow-implement
Exécuter la phase d'Implémentation - développement sprint avec TDD/BDD.
fix
Correction automatisee des bugs identifies par la QA Recette.
hatch3r-bug-pipeline
Run a known-cause bug fix through a 3-phase test-first pipeline -- reproduce + root-cause, regression-test + fix together, then root-cause-depth review -- with full sub-agent delegation.
ralph.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.
feature-implement-execute
Phase 4 of develop: Execute the implementation plan with per-task TDD, quality gates, and completion verification.
speckit.tdd.plan
Derive the feature's test list by delegating to zfa tdd plan (deterministic engine); falls back to LLM-guided derivation only when zfa is unavailable.