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 skills add zekiriabd/SDD-Pro --skill test-driven-developmentgit clone --depth 1 https://github.com/zekiriabd/SDD-ProWrote 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/zekiriabd/sdd-pro/test-driven-development)<a href="https://agentmods.dev/skills/zekiriabd/sdd-pro/test-driven-development"><img src="https://agentmods.dev/badge/skills/zekiriabd/sdd-pro/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.00141 | $0.01804 |
| Opus 5 | $0.00071 | $0.00902 |
| Sonnet 5 | $0.00028 | $0.00361 |
| Haiku 4.5 | $0.00014 | $0.00180 |
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 3d 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill — Test-Driven Development (RED-GREEN-REFACTOR)
Emprunt direct Superpowers v5.1 : "NO PRODUCTION CODE WITHOUT A FAILING TEST FIRST. Delete code written before tests — start over." Ce skill matérialise le contrat test-first au niveau du pipeline SDD_Pro, complémentaire au QA agent (qui RUN les tests) et à l'API Gate (qui les vérifie post-hoc).
L'invariant non-négociable
RED → écrire UN test qui échoue (et le faire échouer pour la bonne raison)
GREEN → écrire le code MINIMAL pour le passer
REFACTOR → améliorer code + tests tant que tests restent verts
Aucune ligne de code de production sans un test écrit avant qui le justifie. Si l'agent réalise qu'il a écrit du code sans test : supprimer le code, écrire le test, recommencer en RED.
Quand ce skill s'active
| Intention détectée | Action TDD |
|---|---|
| "Écris une fonction qui …" | Skill bloque → "écris d'abord le test qui définit le contrat" |
| "Ajoute un endpoint POST /api/foo" | Skill bloque → "écris d'abord le test d'intégration HTTP du happy path" |
"Crée une classe UserService" |
Skill bloque → "écris d'abord 1 test du method principal" |
| Création fichier `*.cs | *.ts |
| "Je vais refactor X" | Skill ALLOWS (refactor = test reste vert ; pas de nouveau contrat) |
| "Je vais corriger un bug" | Skill exige un test de régression rouge AVANT le fix |
Le cycle complet (étapes)
1. RED — écrire le test rouge
- Identifier l'unité minimale à tester (1 behavior, pas N)
- Écrire le test dans le bon répertoire :
- .NET :
workspace/src/{BackendName}.Tests/Unit/ - Node/TS :
__tests__/ou*.test.tsà côté - Python :
tests/test_*.py - Kotlin :
src/test/kotlin/
- .NET :
- Lancer le test, vérifier qu'il échoue — et qu'il échoue pour la bonne raison (assertion failure, pas import error / syntax error)
- Si le test passe immédiatement → soit le code existe déjà, soit le test ne teste rien. STOP, repenser.
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.
- 3d ago First seen · 121 lines · 141 tokens per session scan A 52913a3e1312
test-driven-development is a skill published in the GitHub repository zekiriabd/SDD-Pro (191 stars, last pushed 4d ago), licensed Apache-2.0. It adds 141 tokens to every session and 1,804 once invoked, about $0.0007 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
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.
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.
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.