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 Vimalk0703/shipworthy --skill test-driven-developmentgit clone --depth 1 https://github.com/Vimalk0703/shipworthyWrote 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/vimalk0703/shipworthy/test-driven-development)<a href="https://agentmods.dev/skills/vimalk0703/shipworthy/test-driven-development"><img src="https://agentmods.dev/badge/skills/vimalk0703/shipworthy/test-driven-development/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/vimalk0703/shipworthy/test-driven-development"><img src="https://agentmods.dev/badge/skills/vimalk0703/shipworthy/test-driven-development.svg" alt="Reviewed on agentmods" width="80" 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.00055 | $0.02135 |
| Opus 5.5 | $0.00022 | $0.00854 |
| Sonnet 5.5 | $0.00011 | $0.00427 |
| Haiku 4.5 | $0.00006 | $0.00214 |
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 1mo 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 — 218 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test-Driven Development
The Iron Rule
NO PRODUCTION CODE WITHOUT A FAILING TEST FIRST — for code that matters.
This rule applies absolutely to: business logic, authentication, payments, data mutations, API endpoints, and calculations. No exceptions, no matter who's asking or how small the change seems.
For everything else, the approach adapts to the situation.
Tier-Adapted Testing Modes
Invisible TDD (Builder-Tier Users)
Builder-tier users care that things work, not how you verified they work. When working with Builder-tier users:
Do this:
- Write tests. Always write tests for anything meaningful.
- Run them. Make sure they pass.
- Report results in outcome language: "I built the payment flow and verified it works correctly — handles successful charges, declined cards, and network errors."
- If something breaks, say: "I found an issue with how refunds were handled and fixed it."
Don't do this:
- "I wrote 3 failing tests to establish the RED state..."
- "Achieved GREEN state on all test cases..."
- "Now entering the REFACTOR phase..."
- "Test coverage is at 87.3% across 12 test suites..."
The tests still exist. The discipline still happens. The user just doesn't need a play-by-play of your testing methodology. They need to know their product works.
How to report:
| Instead of | Say |
|---|---|
| "Wrote 5 unit tests for the auth module" | "Built the login system and verified it handles email/password, Google sign-in, and invalid credentials correctly" |
| "RED: 3 failing tests for payment processing" | "Working on the payment flow now" |
| "All 12 tests passing, 94% coverage" | "Payment processing is working — tested with successful charges, declines, and edge cases" |
| "Added regression test for bug #234" | "Fixed the bug and made sure it won't come back" |
Pragmatic TDD (Quick Fixes, Any Tier)
Some changes don't need formal TDD. Applying RED-GREEN-REFACTOR to a CSS color change is like wearing a hard hat to check the mailbox.
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.
- 1mo ago First seen · 218 lines · 55 tokens per session scan A 764272f2d090
test-driven-development is a skill published in the GitHub repository Vimalk0703/shipworthy (6 stars, last pushed 6mo ago), licensed MIT. It adds 55 tokens to every session and 2,135 once invoked, about $0.0002 per session on Opus 5.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
dare-execute
Executa uma task específica com implementação de código e testes. Use quando o usuário aprovar TASKS.md e quiser executar uma task. Implementa o código, roda testes (Ralph Loop) e valida até passar.
plan-pipeline-execute
Execute a validated plan: worktree isolation, TDD scaffolding, level-based parallel agents, quality gate with smoke test, PR creation and merge. Handles everything through to merged PR.
agent-test-generator
Specialist subagent: Generates comprehensive test suites using TDD patterns. Use only when the user explicitly asks for tests, improved coverage, or test-first development.
python-testing
Expert in Python testing with pytest and test-driven development.
testing-strategy
Design test strategies and test plans with coverage targets. Complements /draft:coverage which measures what this skill plans. Auto-loaded by /draft:implement before TDD.
atomic-tdd
Test-first discipline. Auto-triggers on "let's implement X", "add feature Y", "fix bug Z", "write a test for", "implement", "build out", and similar pre-code-change phrases. Iron rule: failing test exists before production code. Skip only for pure docs/config changes with an explicit "skipped because:" note. Explicit…