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.
npx agentmods add skills/forest6511/claude-code-recipes-v2/tddnpx skills add forest6511/claude-code-recipes-v2 --skill tddgit clone --depth 1 https://github.com/forest6511/claude-code-recipes-v2Wrote 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/skills/forest6511/claude-code-recipes-v2/tdd)<a href="https://agentmods.dev/skills/forest6511/claude-code-recipes-v2/tdd"><img src="https://agentmods.dev/badge/skills/forest6511/claude-code-recipes-v2/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.00027 | $0.00504 |
| Opus 5 | $0.00014 | $0.00252 |
| Sonnet 5 | $0.00005 | $0.00101 |
| Haiku 4.5 | $0.00003 | $0.00050 |
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
実装したい機能: $ARGUMENTS
TDD のサイクルに従い、各フェーズでユーザーの確認を待って次へ進みます。
Phase 1: Red — 失敗するテストを書く
- 機能の最小単位を1つ選び、それに対するテストを書く
- テストを実行し、期待通りに失敗することを確認する (
npm test/pytest/go test) - 失敗メッセージと、次に Green で実装すべき最小スコープをユーザーに報告
Phase 2: Green — テストを通す最小実装
- Phase 1 のテストを通すための最小限のコードだけ書く
- テストを実行し、対象テストが通ることを確認する
- 既存テストが壊れていないことも合わせて確認
- 結果をユーザーに報告
Phase 3: Refactor — 重複の除去と命名の調整
- Phase 2 で書いたコードと既存コードの間に重複がないか調査
- 命名・関数長・責務分離を見直す
- 各リファクタ後にテストを実行し、Green を維持
- 完了をユーザーに報告し、次の機能単位に進むか確認
守るべきルール
- フェーズの順序は厳守。Green の前に余計な実装を進めない
- 各フェーズの最後に必ずテストを実行し、状態を報告する
- ユーザーから「次へ」と指示がない限り次のフェーズに進まない
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 · 34 lines · 27 tokens per session scan A e2b11d7c4ab2
tdd is a skill published in the GitHub repository forest6511/claude-code-recipes-v2 (5 stars, last pushed 4mo ago), licensed MIT. It adds 27 tokens to every session and 504 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 skills, from other repositories
engram-testing-coverage
TDD and coverage standards for Engram. Trigger: When implementing behavior changes in any package.
nw-fp-clojure
Clojure language-specific patterns, data-first modeling, REPL-driven development, and spec.
strict-tdd
Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.
conductor-implement
Execute tasks from a track's implementation plan following TDD workflow.
tdd
This skill should be used when the user wants to implement features or fix bugs using test-driven development. Enforces the RED-GREEN-REFACTOR cycle with vertical slicing, context isolation between test writing and implementation, human checkpoints, and auto-test feedback loops. Uses multi-agent orchestration with the…
mobiai-mobile-tdd
You MUST use this before writing any implementation code for a mobile feature, bug fix, refactor, or behavior change. Tests come before implementation — no exceptions.