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/dev)<a href="https://agentmods.dev/commands/gerard-labs/superpowers-api-platform/dev"><img src="https://agentmods.dev/badge/commands/gerard-labs/superpowers-api-platform/dev/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/dev"><img src="https://agentmods.dev/badge/commands/gerard-labs/superpowers-api-platform/dev.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.00035 | $0.00458 |
| Opus 5.5 | $0.00014 | $0.00183 |
| Sonnet 5.5 | $0.00007 | $0.00092 |
| Haiku 4.5 | $0.00003 | $0.00046 |
Grade A, and why
dev 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
You are the Dev stage coordinator. The architecture plan to implement is in .claude/last-api-plan.md.
Step 1 — Read the plan
Read .claude/last-api-plan.md
Note the **API Platform area:** declared in the plan header. The implementer will use it to detect which gerard:* skills to invoke (and which <project>:* overrides to check via Glob).
Step 2 — Read REQUEST_CHANGES feedback if any
If this is an iteration of a REQUEST_CHANGES loop:
Read .claude/last-api-review.md
Pass the reviewer's findings to the implementer so it can address them specifically.
Step 3 — Invoke api-platform-implementer via Task
Pass:
- The plan (read at step 1)
- The reviewer feedback (if iteration)
The implementer MUST:
- Read state files first
- Detect API Platform area + project skill overrides
- Read relevant
gerard:api-platform-*skills BEFORE editing - Implement the change (resource + DTOs + provider/processor + filters + tests)
- Run
./vendor/bin/phpunit --filter=Apiuntil green - Run
./vendor/bin/phpstan analyse - Run
./vendor/bin/infection --filter=<critical-classes>on changed critical classes - Apply AppSec mitigations from the plan
- Self-audit Y/N checklist
- Emit report between
===API-DEV-BEGIN===/===API-DEV-END===
Step 4 — Persist state file
Write .claude/last-api-dev-report.md with the full content between ===API-DEV-BEGIN=== and ===API-DEV-END=== (exclude markers themselves).
Surface to the user:
Dev done. Run /test 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.
- 1mo ago First seen · 54 lines · 35 tokens per session scan A 2236a26b5a54
dev is a command published in the GitHub repository gerard-labs/superpowers-api-platform (2 stars, last pushed 5mo ago), licensed MIT. It adds 35 tokens to every session and 458 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-doctrine-relations
Guide for implementing Doctrine entity relationships (OneToMany, ManyToMany).
symfony-api-resources
Configure API Platform resources with operations and pagination.
symfony-cache
Implement caching strategies using Symfony Cache component.
symfony-messenger
Implement async message handling with Symfony Messenger.
symfony-voters
Implement authorization logic using Symfony Voters.
better-auth:add-plugin
Add a better-auth plugin to an existing project. Configures server and client plugins with proper imports.