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 skills add dev-toolings/superpowers-symfony --skill tdd-with-phpunitgit 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/skills/dev-toolings/superpowers-symfony/tdd-with-phpunit)<a href="https://agentmods.dev/skills/dev-toolings/superpowers-symfony/tdd-with-phpunit"><img src="https://agentmods.dev/badge/skills/dev-toolings/superpowers-symfony/tdd-with-phpunit/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/skills/dev-toolings/superpowers-symfony/tdd-with-phpunit"><img src="https://agentmods.dev/badge/skills/dev-toolings/superpowers-symfony/tdd-with-phpunit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00042 | $0.00499 |
| Opus 5.5 | $0.00017 | $0.00200 |
| Sonnet 5.5 | $0.00008 | $0.00100 |
| Haiku 4.5 | $0.00004 | $0.00050 |
Grade A, and why
tdd-with-phpunit 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 20d 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 With Phpunit (Symfony)
Use when
- Driving a feature with RED-GREEN-REFACTOR using PHPUnit 10/11 class-based tests.
- Choosing between
TestCase,KernelTestCaseandWebTestCasefor a new behavior. - Testing a console command, or an invalid form that must answer 422.
- Swapping an external service for a double through the test container.
Default workflow
- RED: pick the base class, write the test with
#[Test],#[DataProvider]and#[CoversClass], run it and check it fails for the right reason. - GREEN: write the minimum code that passes.
- REFACTOR with the suite green, re-running it after each change.
- Replace an external boundary with
static::getContainer()->set(Service::class, $mock). - Test commands with
CommandTester, or withrunCommand()andassertCommandIsSuccessful()on Symfony 8.1+. - Assert invalid form submissions with
assertResponseIsUnprocessable().
Guardrails
- Use PHPUnit 10+ attributes, not
@testor@dataProviderannotations. - Fetch services with
static::getContainer(), not the legacyself::$container. - Mock only true external boundaries (HTTP clients, third-party SDKs); keep real services and a real database elsewhere.
runCommand()and closures ingetContainer()->set()need Symfony 8.1+.
Progressive disclosure
- Use this file for execution posture and risk controls.
- Open references when deep implementation details are needed.
Output contract
- The failing PHPUnit output (RED), then the passing run.
- Test files changed, with the base class and attributes used.
- Commands executed.
References
reference.md
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 20d ago Changed · +4 lines 53f4e4d26e0c
- 1mo ago Changed · +3 lines · -2 tokens per session 66c60cf5c15d
- 1mo ago First seen · 42 lines · 44 tokens per session scan A eec25e726eca
tdd-with-phpunit is a skill published in the GitHub repository dev-toolings/superpowers-symfony (226 stars, last pushed 20d ago), licensed MIT. It adds 42 tokens to every session and 499 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-09-03.
Other skills, from other repositories
test-audit
Audit test suites for T1-T4 violations using AST analysis, mock detection, and multi-stage synthesis. Invoke when user asks to audit tests, check test quality, find mock violations, review test effectiveness, or inspect test suites for over-mocking. Triggers automatic rewrites when quality gates fail.
tdd
Test-driven development with the red-green-refactor loop.
ccc-e2e
Pre-release assessment that fans out via $ccc-fleet into up to three isolated workers (QA audit, unit tests, Playwright E2E) running $ccc-testing lanes, then writes a severity-ranked PASS or FAIL verdict. Use when about to tag a release, after a large merge, or asking is this ready.
ccc-testing
Testing domain router: picks the lane for TDD, E2E, visual regression, load testing, QA, regression checks, evals or verification and runs test-writing work in an isolated worktree. Use when the user asks to write tests, plan a test strategy, or test, verify or load-test a change.
execute
Execute the next available tracked task with TDD, pre-commit validation, PR workflow, AI code review, and issue tracker bridge sync. Primary execution interface for multi-session feature work.
tdd
Use before implementation when behavior can be verified by automated tests and regression coverage has clear value. For bugs with an unknown root cause, use systematic-debugging first, then return for red-green. Follow red-green-refactor—write a failing test first, add only enough code to pass it, then refactor. Do…