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/gerard-labs/superpowers-api-platformWrote 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/gerard-labs/superpowers-api-platform/test)<a href="https://agentmods.dev/commands/gerard-labs/superpowers-api-platform/test"><img src="https://agentmods.dev/badge/commands/gerard-labs/superpowers-api-platform/test/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/gerard-labs/superpowers-api-platform/test"><img src="https://agentmods.dev/badge/commands/gerard-labs/superpowers-api-platform/test.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.00032 | $0.00396 |
| Opus 5.5 | $0.00013 | $0.00158 |
| Sonnet 5.5 | $0.00006 | $0.00079 |
| Haiku 4.5 | $0.00003 | $0.00040 |
Grade A, and why
test 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 2mo 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
You are the Test stage coordinator. Inputs:
.claude/last-api-plan.md— the architecture plan (with test matrix).claude/last-api-dev-report.md— the dev implementation report (lists classes touched)
Step 1 — Read state files
Read .claude/last-api-plan.md # extract test matrix
Read .claude/last-api-dev-report.md # identify critical classes touched
Step 2 — Invoke symfony-tdd-coach via Task
The tdd-coach MUST follow the gold-standard workflow:
- Read state files first (architects test matrix is the contract)
- Run
./vendor/bin/phpunit --filter=Api→ iterate until green - Run
./vendor/bin/infection --filter=<critical-classes>→ identify escaped mutants on critical paths - For each killable escapee: Write the killing test (force the invariant), re-run mutation
- Emit checklist
AC → test path → statuscovering THE WHOLE matrix - Anti-tautology audit on new tests
- Emit report between
===API-TEST-BEGIN===/===API-TEST-END===
No "recommend follow-up" on critical paths — kill or reject (the dev report is bounced back).
Step 3 — Persist state file
Write .claude/last-api-test-report.md with the full content between ===API-TEST-BEGIN=== and ===API-TEST-END=== (exclude markers themselves).
Surface to the user:
Tests done. Run /review next.
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.
- 2mo ago First seen · 41 lines · 32 tokens per session scan A c03c70bacb95
test is a command published in the GitHub repository gerard-labs/superpowers-api-platform (2 stars, last pushed 5mo ago), licensed MIT. It adds 32 tokens to every session and 396 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-31.
Other commands, from other repositories
symfony-tdd-pest
Start a TDD workflow using Pest PHP for Symfony with RED-GREEN-REFACTOR cycle.
symfony-tdd-phpunit
Start a TDD workflow using PHPUnit for Symfony with RED-GREEN-REFACTOR cycle.
atdd
Start the ATDD workflow for a new feature. Optionally provide a feature description as an argument.
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.
bugfix
TDD-driven bugfix workflow: tester writes failing test (RED) → developer fixes (GREEN) → developer refactors (REFACTOR) → reviewer validates. Accepts issue number, description, or both. Asks before pushing and creating a PR; --no-pr commits locally without asking.
ccc-feature-start
Kick off a feature: research context, create an isolated branch, confirm a green baseline, write a task breakdown, and the first failing test. Use when starting new feature work in a git repository.