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/mb-mal/claudecode-dev-skills/test-driven-developmentnpx skills add mb-mal/claudecode-dev-skills --skill test-driven-developmentgit clone --depth 1 https://github.com/mb-mal/claudecode-dev-skillsWhat 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.00050 | $0.00801 |
| Opus 5 | $0.00025 | $0.00400 |
| Sonnet 5 | $0.00010 | $0.00160 |
| Haiku 4.5 | $0.00005 | $0.00080 |
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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test-Driven Development
Generate code that passes provided tests, or create tests first then implement.
Workflow
When user provides tests
- Analyze tests: Understand expected inputs, outputs, and edge cases
- Identify requirements: Extract implicit requirements from test assertions
- Implement solution: Write minimal code that passes all tests
- Verify: Run tests to confirm implementation
- Refactor: Improve code while keeping tests green
When user describes behavior
- Clarify requirements: Ask for specific input/output examples
- Write tests first: Create tests covering happy path and edge cases
- Present tests: Show tests to user for confirmation
- Implement: Write code that passes tests
- Iterate: Add tests for additional cases as needed
Prompting for test cases
When user provides vague requirements, ask:
- What inputs does this function accept?
- What should it return for a typical case?
- What edge cases should be handled? (empty input, null, boundaries)
- What errors should be raised and when?
Test template
import pytest
class TestCalculateDiscount:
"""Tests for discount calculation logic."""
def test_no_discount_for_small_order(self):
"""Orders under threshold receive no discount."""
assert calculate_discount(amount=500) == 0
def test_5_percent_discount_over_1000(self):
"""Orders over 1000 receive 5% discount."""
assert calculate_discount(amount=1500) == 75
def test_10_percent_discount_over_5000(self):
"""Orders over 5000 receive 10% discount."""
assert calculate_discount(amount=6000) == 600
def test_zero_amount_returns_zero(self):
"""Zero order amount returns zero discount."""
assert calculate_discount(amount=0) == 0
def test_negative_amount_raises_error(self):
"""Negative amounts are invalid."""
with pytest.raises(ValueError):
calculate_discount(amount=-100)
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 · 116 lines · 50 tokens per session scan A 6050b02d09be
test-driven-development is a skill published in the GitHub repository mb-mal/claudecode-dev-skills (5 stars, last pushed 7mo ago), licensed Apache-2.0. It adds 50 tokens to every session and 801 once invoked, about $0.0003 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.