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 commands/penwyp/claudepreference/m-tdd-plannergit clone --depth 1 https://github.com/penwyp/ClaudePreferenceWrote 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/commands/penwyp/claudepreference/m-tdd-planner)<a href="https://agentmods.dev/commands/penwyp/claudepreference/m-tdd-planner"><img src="https://agentmods.dev/badge/commands/penwyp/claudepreference/m-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 | $0.00000 | $0.00645 |
| Opus 5 | $0.00000 | $0.00322 |
| Sonnet 5 | $0.00000 | $0.00129 |
| Haiku 4.5 | $0.00000 | $0.00064 |
Grade A, and why
m-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 5d 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TDD Plan Workflow: Generate Test-First Development Plan
Target: $ARGUMENTS (Default: requirement document(s) in the default project location)
Scope: Analyze requirements and generate comprehensive TDD implementation plan
Execution Steps
-
Requirements Analysis
- Parse target documents and extract testable requirements
- Identify behavioral specifications and acceptance criteria
- Document ambiguous requirements for clarification
-
Test Strategy Design
- Define test pyramid structure (Unit, Integration, E2E)
- Select appropriate testing frameworks and tools
- Outline test infrastructure and environment setup
-
TDD Task Decomposition
- Break down features into Red → Green → Refactor cycles
- Create specific test scenarios for each requirement
- Sequence tasks based on dependency relationships
-
Task Dependency Mapping
- Identify prerequisite relationships between test tasks
- Establish logical order for TDD implementation
- Plan for parallel test development opportunities
-
Plan Visualization
- Generate Mermaid diagram showing task flow and dependencies
- Illustrate Red-Green-Refactor cycles visually
- Highlight critical testing milestones
-
Generate TDD Plan Report
- Compile structured JSON output with all components
- Validate completeness of test coverage strategy
Output Format
Return a JSON object with the following structure:
{
"testStrategy": "string - Overall testing approach, frameworks, and infrastructure description",
"tasks": [
{
"id": "string",
"description": "string - Specific Red/Green/Refactor step description",
"type": "red|green|refactor|setup|integration",
"status": "pending|in-progress|completed",
"dependencies": ["task_id_1", "task_id_2"],
"testLevel": "unit|integration|e2e"
}
],
"diagram": "string - Mermaid diagram code showing task dependencies and TDD flow",
"clarifications": [
"string - Questions about ambiguous requirements or testing approach"
]
}
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.
- 5d ago First seen · 96 lines · 0 tokens per session scan A 138327b4a96f
m-tdd-planner is a command published in the GitHub repository penwyp/ClaudePreference (137 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 645 tokens. 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 commands, from other repositories
tdd-requirements
TDD開発の要件整理を行います。機能要件を明確化し、テスト駆動開発のための準備を行います。.
pm-auto-design2dev
設計レビューから実装完了まで完全自動化(設計レビュー→作業計画→TDD実装).
avance-rapido
Crear todos los artefactos de planificación de un golpe (fast-forward).
dashboard
Generar dashboard HTML local con métricas de eficiencia del proyecto SDD.
usage-add
PitWay: Accumulate measured planning or qa token usage onto a milestone.
hub-tdd
TDD workflow for MCP Hub implementation. Types → Tests (red) → Implementation (green) with git gates.