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/drizzy07x/skillquiver/test-driven-developmentnpx skills add Drizzy07x/Skillquiver --skill test-driven-developmentgit clone --depth 1 https://github.com/Drizzy07x/SkillquiverWhat 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.00676 |
| Opus 5 | $0.00013 | $0.00338 |
| Sonnet 5 | $0.00005 | $0.00135 |
| Haiku 4.5 | $0.00003 | $0.00068 |
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.
How it starts
The opening of the file, as written. The whole thing — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test-Driven Development
Write one behavioral test, observe the expected failure, write the minimum code to pass, and refactor only while green.
Scope
Use TDD for features, bug fixes, and externally observable behavior changes. For a pure behavior-preserving refactor, preserve existing green tests and add coverage only for an uncovered contract the refactor could break. Ask before skipping TDD for throwaway prototypes, generated code, or configuration-only changes.
Production code written before its failing test is not a red-green cycle. Do not keep it as a reference: revert that implementation, establish red, and implement from the test.
Cycle
1. Red
Write the smallest test that expresses one required behavior through the highest practical public seam.
- Name the behavior precisely.
- Exercise real production code; mock only an external boundary that cannot be used safely or deterministically.
- Cover the requested example first, then one meaningful edge or error case.
- Run only the focused test while iterating.
Record the command, non-zero exit, and decisive assertion output. Confirm that the test failed because the behavior is missing, not because of syntax, setup, imports, or the wrong command. A passing test or a test that errors does not establish red; correct it and rerun.
2. Green
Implement only enough production behavior to satisfy the red test. Do not add options, abstractions, validation, or adjacent cleanup that no current test or requirement demands.
Rerun the identical focused command. Fix production code rather than weakening the assertion. Record the zero exit and passing output. If existing focused tests now fail, resolve the regression before continuing.
3. Refactor
Only after green, remove duplication, improve names, or simplify structure without adding behavior. Keep the focused tests green after every structural change. If the next requirement needs new behavior, start another red cycle.
Test integrity
Before writing or changing a non-trivial test, read writing-good-tests.md. In particular:
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 · 86 lines · 26 tokens per session scan A c35df5f6be28
test-driven-development is a skill published in the GitHub repository Drizzy07x/Skillquiver (2 stars, last pushed 10d ago), licensed MIT. It adds 26 tokens to every session and 676 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-31.
Other skills, from other repositories
agent-integration
Run all three agent integration phases sequentially: research, write-tests, and implement using E2E-first TDD (unit tests written last). For individual phases, use /agent-integration:research, /agent-integration:write-tests, or /agent-integration:implement. Use when the user says "integrate agent", "add agent…
engram-testing-coverage
TDD and coverage standards for Engram. Trigger: When implementing behavior changes in any package.
code-assist
Guides implementation of code tasks using test-driven development in an Explore, Plan, Code, Commit workflow. Acts as a Technical Implementation Partner and TDD Coach — following existing patterns, avoiding over-engineering, and producing idiomatic, modern code.
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.
css-design-tdd
Test-driven CSS design system modifications. Run checks before/after CSS changes to verify token usage, variable definitions, fallbacks, and consistency. Use when modifying CSS tokens, fixing design inconsistencies, or auditing CSS architecture.
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.