Borrowing it
Nothing to install: this file belongs to changoo89/claude-pilot. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/changoo89/claude-pilot/main/.claude/skills/tdd/SKILL.mdgit clone --depth 1 https://github.com/changoo89/claude-pilotWrote 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/changoo89/claude-pilot/tdd)<a href="https://agentmods.dev/skills/changoo89/claude-pilot/tdd"><img src="https://agentmods.dev/badge/skills/changoo89/claude-pilot/tdd/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/changoo89/claude-pilot/tdd"><img src="https://agentmods.dev/badge/skills/changoo89/claude-pilot/tdd.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.00054 | $0.00697 |
| Opus 5.5 | $0.00022 | $0.00279 |
| Sonnet 5.5 | $0.00011 | $0.00139 |
| Haiku 4.5 | $0.00005 | $0.00070 |
Grade A, and why
tdd 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 2mo 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SKILL: Test-Driven Development (TDD)
Purpose: Execute TDD Red-Green-Refactor cycle for feature implementation Target: Coder teammates implementing features with test-first methodology in Agent Teams ⚠️ Teammates Only: This skill is for coder teammates in Agent Teams. Team Lead delegates via teammate spawn.
Quick Start
When to Use This Skill
- Implement new feature with test coverage
- Fix bug with regression tests
- Refactor code with test safety net
Quick Reference
# Red: pytest tests/test_feature.py -k "SC-1" # FAIL
# Green: [Implement feature]
# Refactor: [Refactor code]
# Verify: pytest # ALL PASS
What This Skill Covers
In Scope
- Red-Green-Refactor cycle execution
- Test-first development methodology
- Minimal implementation for Green phase
Out of Scope
- Test framework selection → @.claude/skills/tdd/REFERENCE.md
- Coverage thresholds → @.claude/skills/ralph-loop/SKILL.md
- Code quality standards → @.claude/skills/vibe-coding/SKILL.md
Core Concepts
The TDD Cycle: Red-Green-Refactor
Phase 1: Red - Write Failing Test
def test_add_two_numbers():
result = calculator.add(2, 3)
assert result == 5
Run test → Confirm it FAILS (❌)
Phase 2: Green - Minimal Implementation
def add(a, b):
return a + b # Just enough to pass
Run test → Confirm it PASSES (✅)
Phase 3: Refactor - Improve Quality
def add(a: int, b: int) -> int:
"""Add two integers with type safety."""
return a + b
Run ALL tests → Confirm ALL PASS (✅)
Why TDD Matters
- Tests drive design: API designed from usage perspective
- Regression safety: Refactor without fear
- Living documentation: Tests show intended behavior
- Fast feedback: Catch issues immediately
Further Reading
Internal: @.claude/skills/tdd/REFERENCE.md - Advanced TDD concepts, patterns, and examples | @.claude/skills/ralph-loop/SKILL.md - Autonomous completion loop | @.claude/skills/vibe-coding/SKILL.md - Code quality standards | @.claude/skills/tdd/REFERENCE.md - Test framework detection
What ships with it
1 file 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.
- 2mo ago First seen · 79 lines · 54 tokens per session scan A 22adbdf309f4
tdd is a skill published in the GitHub repository changoo89/claude-pilot (20 stars, last pushed 8mo ago), licensed MIT. It adds 54 tokens to every session and 697 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-08-30.
Other skills, from other repositories
accessibility-a11y
WCAG 2.2 compliance, ARIA patterns, keyboard navigation, screen readers, automated testing.
verification-engine
Use when verifying build/test/lint before commit, PR, or completion claims. Runs verification pipeline in fresh subagent context with auto-repair. Triggers on /handoff-verify, pre-commit check, build verification, test validation.
verify-implementation
A workflow that runs a project’s verification skills to produce a report on coding patterns, architecture rules, and project conventions. It is intended for work after implementation, before a pull request, or during code review.
agent-e2e-test-specialist
Specialist subagent: Playwright, Cypress, and visual regression testing specialist. Use only when the user explicitly asks for E2E tests, browser test automation, or visual regression testing. Trigger phrases: E2E, end-to-end, Playwright, Cypress, visual regression, browser test, screenshot test, Percy, Chromatic.
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.
verification-contract
Internal contract: the acceptance artifact per delivery unit — legacy (pre- feature 61) units may carry a frozen ACCEPTANCE.md (binding if present); post-feature 61 units use the unit doc's ## Acceptance criteria section as the canonical acceptance source; the unit doc's evidence carrier — ## Evidence table, or ## Log…