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/intent-driven-dev/intent-driven-template/test-driven-developmentnpx skills add intent-driven-dev/intent-driven-template --skill test-driven-developmentgit clone --depth 1 https://github.com/intent-driven-dev/intent-driven-templateWhat 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.00026 | $0.00333 |
| Opus 5 | $0.00013 | $0.00167 |
| Sonnet 5 | $0.00005 | $0.00067 |
| Haiku 4.5 | $0.00003 | $0.00033 |
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 2d 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.
What it actually says
Test-Driven Development
Use the repository's existing test tooling and conventions.
One test, one behaviour, one reason to fail. A test name describes that one behaviour; never use joiners such as "and", "or", or "etc." to combine independent outcomes. Multiple assertions are acceptable only when together they establish that same behaviour.
Red
- Select one observable behaviour from the requirement.
- Write one test before changing implementation code.
- Run the test and confirm it fails because the behaviour is missing, not because the test is broken.
Green
- Write only enough implementation code to pass the failing test.
- Run the test, then run the relevant suite.
- Do not add behaviour without first seeing its test fail.
Refactor
- Refactor only while the relevant suite is green, after completing a red-green slice.
- Refactor either the tests or the implementation in one pass, not both.
- Reuse shared setup, teardown, helpers, and parameterized structure when they clarify intent without combining behaviours.
- Rerun the relevant suite after each refactor pass.
Patterns and anti-patterns
Read patterns and anti-patterns when choosing a test shape, writing examples, or deciding whether cases belong together.
Collaborators
Read collaborators before substituting a dependency. Mock system boundaries, not code owned by the application.
What ships with it
2 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.
- 2d ago First seen · 41 lines · 26 tokens per session scan A 8687c3dcc1d0
test-driven-development is a skill published in the GitHub repository intent-driven-dev/intent-driven-template (121 stars, last pushed 9d ago), licensed MIT. It adds 26 tokens to every session and 333 once invoked, about $0.0001 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-30.
Other skills, from other repositories
mermaid
Create, validate, and repair Mermaid.js diagrams. Use when generating flowcharts, sequence, class, ER, state, or Gantt diagrams, or any visualization.
teach-me
Turn a 'teach me X' request into a single interactive HTML lesson, rendered Arcade-first, by emitting a lesson data model and assembling it with rp1 tooling.
artifact-templates
Agent-only canonical output templates for rp1 artifacts. Load when producing structured markdown to ensure format consistency and routing metadata.
deep-research
Autonomous deep research on codebases and technical topics with structured report output via map-reduce explorer architecture.
generate-user-docs
Synchronizes user-facing documentation with the current knowledge base through validate -> stale gate -> scan -> approval -> process orchestration.
markdown-preview
Generate browser-viewable HTML previews from markdown, plain text, and Mermaid diagrams. Auto-validates, styles, and opens in browser.