Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/XRenSiu/claude-code-forgeWrote 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/xrensiu/claude-code-forge/tdd)<a href="https://agentmods.dev/commands/xrensiu/claude-code-forge/tdd"><img src="https://agentmods.dev/badge/commands/xrensiu/claude-code-forge/tdd/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/xrensiu/claude-code-forge/tdd"><img src="https://agentmods.dev/badge/commands/xrensiu/claude-code-forge/tdd.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.00000 | $0.02324 |
| Opus 5.5 | $0.00000 | $0.00930 |
| Sonnet 5.5 | $0.00000 | $0.00465 |
| Haiku 4.5 | $0.00000 | $0.00232 |
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 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 — 285 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mission
启动测试驱动开发（TDD）模式。严格执行红-绿-重构循环，确保所有代码都有对应的测试先行。
TDD 铁律
核心原则：没有失败的测试，就没有代码。
┌─────────────────────────────────────────────────────────────────┐
│ TDD 红-绿-重构循环 │
├─────────────────────────────────────────────────────────────────┤
│ │
│ ┌──────────────────────────────────────────────────┐ │
│ │ │ │
│ │ 1. 🔴 红色: 写一个失败的测试 │ │
│ │ └── 运行测试，确认失败 │ │
│ │ │ │
│ │ ↓ │ │
│ │ │ │
│ │ 2. 🟢 绿色: 写最小代码让测试通过 │ │
│ │ └── 运行测试，确认通过 │ │
│ │ │ │
│ │ ↓ │ │
│ │ │ │
│ │ 3. 🔵 重构: 改进代码质量 │ │
│ │ └── 运行测试，确认仍然通过 │ │
│ │ │ │
│ │ ↓ │ │
│ │ │ │
│ │ 返回步骤 1，下一个测试 │ │
│ │ │ │
│ └──────────────────────────────────────────────────┘ │
│ │
└─────────────────────────────────────────────────────────────────┘
语法
/tdd [options]
参数
| 参数 | 类型 | 必需 | 说明 |
|---|---|---|---|
--plan |
string | 否 | 任务计划文件路径 |
--task |
string | 否 | 特定任务 ID |
--coverage |
number | 否 | 最低覆盖率要求（默认 80%） |
--strict |
flag | 否 | 严格模式，任何违规立即停止 |
--mode |
string | 否 | subagent（高质量）或 fast（快速） |
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 · 285 lines · 0 tokens per session scan A 9e817363d140
tdd is a command published in the GitHub repository XRenSiu/claude-code-forge (2 stars, last pushed 29d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,324 tokens. 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-05.
Other commands, from other repositories
bugfix
Bug fix workflow: root cause analysis → user review → regression test + fix via TDD.
eval
Evaluate and improve one healthcare agent's system prompt. Run up to 5 iterations of: prepare fixed questions -> answer -> judge -> improve -> re-score -> commit if better.
usage-add
PitWay: Accumulate measured planning or qa token usage onto a milestone.
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.
tdd
A command that follows test-driven development (TDD), a method where you write tests before the code they check. It moves through writing a failing test, adding the smallest implementation, and then improving the code.
dashboard
Generar dashboard HTML local con métricas de eficiencia del proyecto SDD.