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/commands/dev-toolings/superpowers-symfony/symfony-tdd-pest)<a href="https://agentmods.dev/commands/dev-toolings/superpowers-symfony/symfony-tdd-pest"><img src="https://agentmods.dev/badge/commands/dev-toolings/superpowers-symfony/symfony-tdd-pest/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/commands/dev-toolings/superpowers-symfony/symfony-tdd-pest"><img src="https://agentmods.dev/badge/commands/dev-toolings/superpowers-symfony/symfony-tdd-pest.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.00026 | $0.00055 |
| Opus 5.5 | $0.00010 | $0.00022 |
| Sonnet 5.5 | $0.00005 | $0.00011 |
| Haiku 4.5 | $0.00003 | $0.00006 |
Grade A, and why
symfony-tdd-pest 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- symfony-tdd-pest — 89% identical, 4 lines differ
What it actually says
Use the tdd-with-pest skill exactly as written.
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 · +2 lines · +7 tokens per session e7dc5acd4087
- 1mo ago First seen · 6 lines · 19 tokens per session scan A 13aee5c8d1cf
symfony-tdd-pest is a command published in the GitHub repository dev-toolings/superpowers-symfony (226 stars, last pushed 19d ago), licensed MIT. It adds 26 tokens to every session and 55 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 commands, from other repositories
symfony-tdd-pest
Start a TDD workflow using Pest PHP for Symfony with RED-GREEN-REFACTOR cycle.
symfony-check
Run all quality checks (PHP-CS-Fixer, PHPStan, tests) on the Symfony project.
cpp-test
Enforce TDD workflow for C++. Write GoogleTest tests first, then implement. Verify coverage with gcov/lcov.
go-test
Go TDD workflow with table-driven tests.
rust-test
Rust TDD workflow with unit and property tests.
debug
Systematic root-cause investigation, then fix with TDD — never proposes a fix before finding the cause; resumable diagnosis + regression test in .orc/ state. Workspace-aware. For a quick one-off look without session state, prefer the bundled /debug.