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/orlando-japan/claude-code-setting/tddnpx skills add orlando-japan/claude-code-setting --skill tddgit clone --depth 1 https://github.com/orlando-japan/claude-code-settingWrote 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/orlando-japan/claude-code-setting/tdd)<a href="https://agentmods.dev/skills/orlando-japan/claude-code-setting/tdd"><img src="https://agentmods.dev/badge/skills/orlando-japan/claude-code-setting/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.00032 | $0.00604 |
| Opus 5 | $0.00016 | $0.00302 |
| Sonnet 5 | $0.00006 | $0.00121 |
| Haiku 4.5 | $0.00003 | $0.00060 |
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 5d 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test-driven development
TDD isn't ideology — it's a tool. Use it where it earns its keep.
Use TDD when
- The interface is clear (input → output), the algorithm is what's uncertain.
- You're fixing a bug (write the failing test that reproduces, then fix).
- You're touching load-bearing code without existing test coverage.
Don't use TDD when
- The interface itself is exploratory — write a sketch first, then tests once the shape settles.
- You're doing throwaway research / spikes.
- The cost of testing exceeds the cost of rewriting (rare in practice, real in prototyping).
The cycle
Red:
- Write one test for the next smallest unverified behavior.
- Run it. It must fail, and fail for the expected reason ("function not defined" is fine; "typo in import" is not — fix the typo, re-run).
Green:
- Write the simplest code that makes this test pass. Not the cleanest, not the most general — the simplest.
- Run the test. Green.
- Run all the previous tests. Still green.
Refactor:
- Look at the code. Can you remove duplication without changing behavior?
- Refactor. Run the tests after every change, not at the end.
- If a refactor breaks tests, the refactor was wrong — revert.
Repeat.
Rules
- One test at a time. No batching "let me write ten tests first."
- One assertion per concept (not per line). A test for "login redirect" can assert location and that the cookie was set — they're one concept.
- Tests name behaviors, not methods.
'redirects logged-out users to /login'beats'test_login_handler'. - Delete failing-and-never-fixed tests. Don't
.skip()and forget. Fix or cut.
Bug-fix TDD
Special case, highly recommended:
- Reproduce the bug with a test (red).
- Confirm the test fails for the bug's reason, not some other reason.
- Fix the bug.
- Test goes green.
- The test is now a regression test; keep it.
This produces bug fixes that can't silently regress.
When tests are hard to write
Hard-to-test code is usually telling you something:
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.
- 5d ago First seen · 76 lines · 32 tokens per session scan A 1a559d254b6d
tdd is a skill published in the GitHub repository orlando-japan/claude-code-setting (2 stars, last pushed 3mo ago), licensed MIT. It adds 32 tokens to every session and 604 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-08-31.
Other skills, from other repositories
test-driven
实现功能或修 bug 前使用。先写会失败的测试,再写实现。.
engram-testing-coverage
TDD and coverage standards for Engram. Trigger: When implementing behavior changes in any package.
nunit-testing
Use when writing or modifying tests in NUnit's own test projects, or when making a behavioral change to production code that needs test coverage. Covers test structure, attribute choice, helper visibility, platform guards, and which test projects are real.
tdd
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
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.