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/madappgang/claude-code/test-driven-developmentnpx skills add MadAppGang/claude-code --skill test-driven-developmentgit clone --depth 1 https://github.com/MadAppGang/claude-codeWrote 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/madappgang/claude-code/test-driven-development)<a href="https://agentmods.dev/skills/madappgang/claude-code/test-driven-development"><img src="https://agentmods.dev/badge/skills/madappgang/claude-code/test-driven-development.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 | $0.00042 | $0.04049 |
| Opus 5 | $0.00021 | $0.02024 |
| Sonnet 5 | $0.00008 | $0.00810 |
| Haiku 4.5 | $0.00004 | $0.00405 |
Grade A, and why
test-driven-development 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 yesterday.
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- test-driven-development — 94% identical, 9 lines differ
How it starts
The opening of the file, as written. The whole thing — 535 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test-Driven Development (TDD)
Iron Law: "NO PRODUCTION CODE WITHOUT A FAILING TEST FIRST"
When to Use
Use this skill when:
- Writing new functions, methods, or classes
- Adding features to existing code
- Fixing bugs (write test that reproduces bug first)
- Refactoring code (tests verify behavior preservation)
- Implementing API endpoints or business logic
- Creating UI components with testable behavior
Red Flags (Violation Indicators)
Watch for these patterns that indicate TDD violations:
- Implementation First - Writing production code before any test exists ("I'll write the function, then add tests")
- "Tests After" Promise - Planning to write tests later ("Let me implement this quickly, I'll add tests after")
- "Same Purpose" Rationalization - Claiming manual testing is equivalent ("I tested it manually, that's the same thing")
- Skipping "Simple" Code - Avoiding tests for "obvious" logic ("This function is too simple to test")
- Happy Path Only - Writing tests only for success cases, ignoring errors ("The normal case works, that's enough")
- No Test for Changes - Modifying code without adding corresponding test ("Just a small change, doesn't need a test")
- "Just a Small Fix" - Bypassing TDD for "quick fixes" ("It's only one line, I don't need a test")
Violation Detection: If you find yourself saying "I'll test this after I get it working," you're violating TDD.
RED-GREEN-REFACTOR Cycle
TDD follows a strict 3-phase workflow:
Phase 1: RED (Write a Failing Test)
Objective: Specify desired behavior through a test that fails
Steps:
- Write the test first - Before any production code exists
- Define expected behavior - What should the code do?
- Use API you wish existed - Test the interface you want
- Run the test - Verify it fails (if it passes, you didn't test new behavior)
- Check failure reason - Ensure it fails for the right reason (missing code, not syntax error)
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.
- yesterday First seen · 535 lines · 42 tokens per session scan A c3d2675e4e90
test-driven-development is a skill published in the GitHub repository MadAppGang/claude-code (279 stars, last pushed 5mo ago), licensed MIT. It adds 42 tokens to every session and 4,049 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
tdd
Test-driven development workflow with philosophy guide - plan → write tests → implement → validate.
test-generator
测试生成技能 - 单元测试创建、Mock生成、覆盖率分析.
software-test-creation
Write failing tests for a TDD slice based on acceptance criteria and codebase conventions. Use when the "red" phase of red-green-refactor requires tests that define expected behavior before implementation exists. Discovers codebase test conventions first, writes test files that compile or parse but fail because the…
jest-patterns
Jest testing patterns, anti-patterns, and quality rules for JavaScript and TypeScript test files (.test.ts, .spec.js, tests). Includes deterministic test-smell detector (jestsmell.py) for .only/.skip left in, missing expects, async-without-await, setTimeout(0), console.log, and done callbacks. Use proactively when…
pytest-patterns
Pytest testing patterns, anti-patterns, and quality rules for Python test files (test.py, test.py, conftest.py). Includes deterministic test-smell detector (pytestsmell.py) for no-assertion tests, empty tests, bare excepts, magic numbers, sleep calls, and print calls. Covers fixtures, parametrize, mock, patch, and…
Unit Test Scaffold (TypeScript)
Generate TypeScript unit test skeletons (Jest/Vitest) from specifications.