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/mshadmanrahman/pm-pilot/tddgit clone --depth 1 https://github.com/mshadmanrahman/pm-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/commands/mshadmanrahman/pm-pilot/tdd)<a href="https://agentmods.dev/commands/mshadmanrahman/pm-pilot/tdd"><img src="https://agentmods.dev/badge/commands/mshadmanrahman/pm-pilot/tdd.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.00019 | $0.00122 |
| Opus 5 | $0.00010 | $0.00061 |
| Sonnet 5 | $0.00004 | $0.00024 |
| Haiku 4.5 | $0.00002 | $0.00012 |
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 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.
What it actually says
/tdd
Start test-driven development for a feature or fix.
Usage
/tdd {feature or behavior to implement}
Behavior
- Invoke the tdd-guide agent from
agents/tdd-guide.md - Write failing test first (RED)
- Implement minimal code to pass (GREEN)
- Refactor and verify coverage (IMPROVE)
- Repeat until feature is complete with 80%+ coverage
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 · 20 lines · 19 tokens per session scan A ca7070f5d1bf
tdd is a command published in the GitHub repository mshadmanrahman/pm-pilot (19 stars, last pushed 14d ago), licensed MIT. It adds 19 tokens to every session and 122 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-30.
Other commands, from other repositories
dev-tdd
Implements a feature by following the TDD (Test-Driven Development) cycle.
work-flow-bugfix
Complete workflow to fix a bug, from diagnosis to deployment.
work-flow-feature
Complete workflow for developing a new feature, from exploration to merge.
work-batch
Autonomous and sequential execution of user stories from a PRD file (JSON or Markdown).
work-quick
Quick workflow for trivial changes (1-3 files, < 50 lines, zero risk).
create-feature-plan
Generate a TDD plan with verbose planning docs and minimal agent execution files using MCP planning tools.