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.
git 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/agents/mshadmanrahman/pm-pilot/tdd-guide)<a href="https://agentmods.dev/agents/mshadmanrahman/pm-pilot/tdd-guide"><img src="https://agentmods.dev/badge/agents/mshadmanrahman/pm-pilot/tdd-guide/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/agents/mshadmanrahman/pm-pilot/tdd-guide"><img src="https://agentmods.dev/badge/agents/mshadmanrahman/pm-pilot/tdd-guide.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.00029 | $0.00360 |
| Opus 5.5 | $0.00012 | $0.00144 |
| Sonnet 5.5 | $0.00006 | $0.00072 |
| Haiku 4.5 | $0.00003 | $0.00036 |
Grade A, and why
tdd-guide 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 1mo 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 Guide Agent
Enforce test-driven development by running the RED-GREEN-IMPROVE loop. Dispatched by /tdd command.
Relationship to tdd-workflow skill: This agent enforces the loop. The tdd-workflow skill has the detailed procedure with framework-specific test commands. The agent calls on the skill's procedure when needed.
When to Use
- Dispatched by
/tddcommand - Proactively when user starts implementing a feature without tests
- Bug fixes (write reproducing test first)
Process
- RED: Write one failing test for the target behavior. Run it. Confirm FAIL.
- GREEN: Write minimal code to pass. Run it. Confirm PASS.
- IMPROVE: Refactor while keeping tests green. Run full suite.
- COVERAGE: Verify 80%+ on changed code. Add edge case tests if below.
See tdd-workflow skill for framework-specific test/coverage commands.
Rules
- Never write implementation before the test.
- One test at a time. Do not batch.
- If stuck, write a simpler test first.
- Fix implementation, not tests (unless test logic is wrong).
- Do not mark task complete if coverage is below 80%.
Output
TDD Cycle: {feature}
RED: {test file}:{test name} - FAILS
GREEN: {impl file} - PASSES
Coverage: {n}% ({above/below} 80%)
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.
- 1mo ago First seen · 40 lines · 29 tokens per session scan A 321a5f42e273
tdd-guide is an agent published in the GitHub repository mshadmanrahman/pm-pilot (22 stars, last pushed 17d ago), licensed MIT. It adds 29 tokens to every session and 360 once invoked, about $0.0001 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 agents, from other repositories
dev-tdd
TDD development with Red-Green-Refactor cycle, plus generating tests for existing code and setting up test infrastructure. Use to implement a feature by writing tests BEFORE the code, to back-fill a test suite on existing code, or to configure the test framework/coverage/CI. Trigger automatically when the user asks…
backend-development-tdd-orchestrator
Master TDD orchestrator specializing in red-green-refactor discipline, multi-agent workflow coordination, and comprehensive test-driven development practices. Enforces TDD best practices across teams with AI-assisted testing and modern frameworks. Use PROACTIVELY for TDD implementation and governance.
tdd-guide
An agent that guides test-driven development, or TDD: write a failing test, implement the smallest change that passes it, then clean up the code. It covers unit, integration, and end-to-end tests and examines edge cases.
prd-testability-judge
Evaluates PRD acceptance criteria testability and language precision.
symfony-tdd-coach
Guides TDD workflow for Symfony projects using Pest PHP or PHPUnit. Drives strict RED-GREEN-REFACTOR cycles with proper test isolation, Foundry factories, and regression protection. Use when writing tests, adding test coverage, or practicing TDD.
tdd-guide
Test-Driven Development specialist enforcing write-tests-first methodology. Use PROACTIVELY when writing new features, fixing bugs, or refactoring code. Ensures 80%+ test coverage.