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/quatico-solutions/agent-skills/test-driven-developmentnpx skills add quatico-solutions/agent-skills --skill test-driven-developmentgit clone --depth 1 https://github.com/quatico-solutions/agent-skillsWrote 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/quatico-solutions/agent-skills/test-driven-development)<a href="https://agentmods.dev/skills/quatico-solutions/agent-skills/test-driven-development"><img src="https://agentmods.dev/badge/skills/quatico-solutions/agent-skills/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.1 | $0.00040 | $0.02598 |
| Opus 5 | $0.00020 | $0.01299 |
| Sonnet 5 | $0.00008 | $0.00520 |
| Haiku 4.5 | $0.00004 | $0.00260 |
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 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 — 359 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test-Driven Development (TDD)
Overview
Write the test first. Watch it fail. Write minimal code to pass.
Core principle: If you didn't watch the test fail, you don't know if it tests the right thing.
Violating the letter of the rules is violating the spirit of the rules.
When to Use
Always:
- New features
- Bug fixes
- Behavior changes
Exceptions (ask your human partner):
- Throwaway prototypes
- Generated code
- Configuration files
- Pure refactoring (no behavior change)
Thinking "skip TDD just this once"? Stop. That's rationalization.
The Iron Law
NO PRODUCTION CODE WITHOUT A FAILING TEST FIRST
Write code before the test? Delete it. Start over. Implement fresh from tests.
Tempted to skip this? That impulse is the thing the rule is for.
Red-Green-Refactor
The TDD cycle with decision points:
digraph tdd_flow {
rankdir=TB;
compound=true;
// Entry point
run_all [label="Run All\nUnit Tests", shape=box, style="filled,rounded", fillcolor="#e8f5e9"];
run_all_decision [label="", shape=diamond, width=0.4, height=0.4];
// RED zone
subgraph cluster_red {
label="Red";
style=filled;
fillcolor="#ffcdd2";
write_test [label="Write failing\nUnit Test", shape=box, style="filled,rounded", fillcolor="#ffebee"];
}
// GREEN zone
subgraph cluster_green {
label="Green";
style=filled;
fillcolor="#c8e6c9";
change_behavior [label="Change\nBehavior", shape=box, style="filled,rounded", fillcolor="#e8f5e9"];
}
// REFACTOR zone
subgraph cluster_refactor {
label="Refactor";
style=filled;
fillcolor="#e0e0e0";
change_structure [label="Change\nStructure", shape=box, style="filled,rounded", fillcolor="#fff9c4"];
}
run_unit [label="Run\nUnit Test", shape=box, style="filled,rounded", fillcolor="#fff9c4"];
run_unit_decision [label="", shape=diamond, width=0.4, height=0.4];
revert [label="Revert\n(test wrong!)", shape=box, style="filled,rounded", fillcolor="#ffccbc"];
run_all -> run_all_decision;
run_all_decision -> change_structure [label="Pass"];
run_all_decision -> write_test [label="Fail"];
write_test -> run_unit;
run_unit -> run_unit_decision;
run_unit_decision -> revert [label="Pass*\n(1st run)"];
run_unit_decision -> change_behavior [label="Fail"];
change_behavior -> run_unit;
run_unit_decision -> change_structure [label="Pass"];
change_structure -> run_all;
}
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 359 lines · 40 tokens per session scan A 4d06041f8850
test-driven-development is a skill published in the GitHub repository quatico-solutions/agent-skills (2 stars, last pushed yesterday), licensed MIT. It adds 40 tokens to every session and 2,598 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
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.
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…
conductor-implement
Execute tasks from a track's implementation plan following TDD workflow.