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 d-mariano/spicyclaude --skill test-driven-developmentgit clone --depth 1 https://github.com/d-mariano/spicyclaudeWrote 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/d-mariano/spicyclaude/test-driven-development)<a href="https://agentmods.dev/skills/d-mariano/spicyclaude/test-driven-development"><img src="https://agentmods.dev/badge/skills/d-mariano/spicyclaude/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.00091 | $0.01318 |
| Opus 5 | $0.00046 | $0.00659 |
| Sonnet 5 | $0.00018 | $0.00264 |
| Haiku 4.5 | $0.00009 | $0.00132 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test-Driven Development — Agent Protocol
TDD is a design discipline. Tests drive the implementation, not the other way around. Every piece of functional code is preceded by a failing test. No exceptions unless the work is purely configuration, documentation, or type-only definitions.
Step 0: Discover the Project's Test Setup
Before writing anything, understand the existing test infrastructure.
- Find the test framework. Look for config files:
jest.config.*,vitest.config.*,pytest.ini,pyproject.toml [tool.pytest],go.test,Cargo.toml,.rspec, etc. - Find existing tests. Search for test directories:
__tests__/,tests/,test/,spec/, or co-located*.test.*/*.spec.*files. Match the existing convention. - Find the test command. Check
package.jsonscripts,Makefile,Taskfile, or README for how to run tests. Common commands:npm test,pytest,go test ./...,cargo test,bundle exec rspec. - If no test setup exists, ask the user which framework to use or recommend the ecosystem default (Jest/Vitest for JS/TS, pytest for Python,
testingfor Go, cargo test for Rust). Set it up before proceeding.
Run the existing test suite once to confirm a clean baseline. If tests are failing before you start, stop and tell the user.
Step 1: RED — Write One Failing Test
Pick the smallest behavior to implement. Write exactly one test for it.
Test structure follows Arrange-Act-Assert:
Arrange — set up the system under test and its dependencies
Act — execute exactly one behavior
Assert — verify the expected outcome
If you are acting on multiple things or asserting unrelated outcomes, split into separate tests.
Name tests after behavior, not implementation:
# Good: describes what the system does
test_expired_subscription_denies_access()
test_empty_cart_shows_zero_total()
# Bad: describes how the code works
test_check_expiry_returns_false()
test_get_total_function()
Run the test. It must fail. If it passes, either the behavior already exists or the test is wrong — investigate before continuing.
What ships with it
3 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.
- 6d ago First seen · 136 lines · 91 tokens per session scan A 67016d888c55
test-driven-development is a skill published in the GitHub repository d-mariano/spicyclaude (5 stars, last pushed 1mo ago), licensed MIT. It adds 91 tokens to every session and 1,318 once invoked, about $0.0005 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.