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/smicolon/ai-kit/tdd-plannernpx skills add smicolon/ai-kit --skill tdd-plannergit clone --depth 1 https://github.com/smicolon/ai-kitWrote 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/smicolon/ai-kit/tdd-planner)<a href="https://agentmods.dev/skills/smicolon/ai-kit/tdd-planner"><img src="https://agentmods.dev/badge/skills/smicolon/ai-kit/tdd-planner.svg" alt="Measured on agentmods" 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.00073 | $0.02010 |
| Opus 5 | $0.00036 | $0.01005 |
| Sonnet 5 | $0.00015 | $0.00402 |
| Haiku 4.5 | $0.00007 | $0.00201 |
Grade A, and why
tdd-planner 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 6d 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 — 250 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TDD Planner
Generate high-quality, structured development plans following Test-Driven Development principles for use with the dev-loop command.
Quality Standard
Every plan must meet this checklist before saving:
- Context lists specific items to work on (not just "the feature")
- Success criteria are measurable (numbers, specific behaviors)
- Every task has a file path
- Code snippets show implementation structure
- Verification has expected output (PASS/FAIL + why)
- Self-correction is phase-specific, not generic
- Files to Modify table exists
- New Files to Create table exists
- Stuck handling is framework/task-specific
Reference: See references/good-example.md for expected quality.
Activation Triggers
This skill activates when:
- Planning a feature for iterative development
- Preparing prompts for dev-loop execution
- Breaking down complex tasks into TDD phases
- Creating structured development workflows
Core Principles
- Specificity Over Vagueness - File paths, code snippets, measurable outcomes
- Iteration Over Perfection - Expect multiple passes, not first-draft solutions
- Failures as Data - Red phase tests MUST fail first
- Framework Awareness - Use correct patterns for detected framework
Required Plan Sections
1. Context
## Context
- **Framework**: Flutter / Django / Next.js / etc.
- **Current State**: What exists now
- **Test Command**: `flutter test` / `pytest` / etc.
- **Lint Command**: `flutter analyze` / `ruff check .` / etc.
- **Items to Work On**:
- `ComponentA` (description)
- `ComponentB` (description)
2. Success Criteria (Measurable)
## Success Criteria
- [ ] Login returns JWT token (specific behavior)
- [ ] 81+ tests pass (quantitative)
- [ ] Invalid credentials return 401 (negative case)
- [ ] All tests pass (`flutter test`)
- [ ] Linter clean (`flutter analyze`)
3. File Tables (Required)
What ships with it
3 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.
- 6d ago First seen · 250 lines · 73 tokens per session scan A 34829d53bb54
tdd-planner is a skill published in the GitHub repository smicolon/ai-kit (6 stars, last pushed 2d ago), licensed MIT. It adds 73 tokens to every session and 2,010 once invoked, about $0.0004 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
superpowers
Use when the user wants a disciplined software development workflow with design-first planning, implementation plans, TDD, systematic debugging, code review, or verification-before-completion, adapted from obra/superpowers.
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.
tdd-workflow
Enforce practical Test-Driven Development for code changes in Go services. Use for new features, bug fixes, refactors, API changes, and new modules. Requires Red-Green-Refactor evidence, defect-hypothesis-driven tests, killer cases, and coverage gates (line + risk-path).
typescript-eval
Test TypeScript code snippets before persisting as skills.
test-driven-development
Use when user explicitly requests test-driven development. Triggers: 'TDD', 'write tests first', 'red green refactor', 'test-first', 'start with the test'. Also invoked by develop and executing-plans for implementation tasks. NOT for: full feature work (use develop, which includes TDD internally).
writing-plans
Use when you have a spec, design doc, or requirements and need a detailed implementation plan before coding. Triggers: 'write a plan', 'create implementation plan', 'plan this out', 'break this down into steps', 'convert design to tasks', 'implementation order'. Also invoked by develop during planning. NOT for…