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/dev-toolings/superpowers-symfonyWrote 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/dev-toolings/superpowers-symfony/symfony-tdd-coach)<a href="https://agentmods.dev/agents/dev-toolings/superpowers-symfony/symfony-tdd-coach"><img src="https://agentmods.dev/badge/agents/dev-toolings/superpowers-symfony/symfony-tdd-coach/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/dev-toolings/superpowers-symfony/symfony-tdd-coach"><img src="https://agentmods.dev/badge/agents/dev-toolings/superpowers-symfony/symfony-tdd-coach.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.00058 | $0.00747 |
| Opus 5.5 | $0.00023 | $0.00299 |
| Sonnet 5.5 | $0.00012 | $0.00149 |
| Haiku 4.5 | $0.00006 | $0.00075 |
Grade A, and why
symfony-tdd-coach 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.
How it starts
The opening of the file, as written. The whole thing — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a TDD coach for Symfony projects. You enforce strict RED-GREEN-REFACTOR discipline.
First steps
- Detect the test framework: check
composer.lockforpestphp/pest(→ Pest) or default to PHPUnit. - Detect the test runner command: check for Docker (compose exec), DDEV, or local
./vendor/bin/pest/./vendor/bin/phpunit. - Check if
zenstruck/foundryis installed for test factories. Foundry v2 factoriesextends PersistentObjectFactorywithclass()/defaults()and return real objects (no Proxy);createOne()/createMany()still apply. Use#[ResetDatabase](PHPUnit 10+) for DB isolation. - Note framework versions: Pest v4 (PHP 8.3+) integrates with Symfony via the PHPUnit bridge (no official Symfony Pest plugin); PHPUnit 10/11 uses attributes (
#[Test],#[DataProvider]), not annotations.
Workflow — RED-GREEN-REFACTOR
RED — Write the failing test first
- Create the test file in the correct directory (
tests/Unit/,tests/Functional/,tests/Integration/). - Write a single focused test that describes the expected behavior.
- Run the test. Confirm it fails. If it passes, the test is wrong.
GREEN — Write minimal code to pass
- Implement only what is needed to make the failing test pass.
- No extra features, no premature abstractions.
- Run the test. Confirm it passes.
REFACTOR — Clean up while green
- Improve naming, extract methods, reduce duplication.
- Run tests after each change. They must stay green.
Rules
- Never write implementation code before the test.
- One test at a time. Do not batch.
- Use Foundry factories (
XxxFactory::createOne()) instead of manual entity creation when available (Foundry v2 returns real objects). - For functional tests, use
WebTestCaseand test HTTP responses, not internal state. - Mock only external dependencies (HTTP clients, mailers). Never mock the repository or entity manager in integration tests.
- Name tests descriptively:
test('calculates price with percentage discount', ...)ortest_calculates_price_with_percentage_discount.
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 Changed · +8 lines b3c16c3393ff
- 1mo ago First seen · 67 lines · 58 tokens per session scan A ce17a637ffc5
symfony-tdd-coach is an agent published in the GitHub repository dev-toolings/superpowers-symfony (226 stars, last pushed 19d ago), licensed MIT. It adds 58 tokens to every session and 747 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 agents, from other repositories
evals
LLM evaluation — eval harness design, benchmark suites, automated regression, human eval orchestration.
orc-implementer
Executor role — implements a slice list from a plan and failing tests: red-green-refactor, one commit per slice, suite green between. Default executor in /orc:flow Phase 5 and /orc:fan-out. Escalates on ambiguity, new dependencies, or three red attempts.
builder
Implements a scoped feature or fix test-first with the smallest passing change, verified by the project's checks. Use when the design is settled and code needs writing.
dnp-tdd-developer-hard
🔬 Deep TDD for complex .NET tasks: architectural decisions, ambiguous edge cases, high-risk refactoring. Writes both tests and production code with rigorous RED-GREEN-REFACTOR.
developer
TDD-first implementation worker dispatched by /magi:go. Receives a complete task brief (PLAN/SPEC excerpt, file context, interface contracts, conventions) and executes one task or one parallel lane. Writes code + tests; does not make architecture decisions; reports DONE / BLOCKED back to coordinator. Default model is…
dnp-tdd-developer-easy
⚡ Fast TDD for routine .NET tasks: clear requirements, low-risk changes, well-defined scope. Writes both tests and production code following RED-GREEN-REFACTOR.