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 gerard-labs/superpowers-api-platform --skill functional-testsgit 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/skills/gerard-labs/superpowers-api-platform/functional-tests)<a href="https://agentmods.dev/skills/gerard-labs/superpowers-api-platform/functional-tests"><img src="https://agentmods.dev/badge/skills/gerard-labs/superpowers-api-platform/functional-tests/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/gerard-labs/superpowers-api-platform/functional-tests"><img src="https://agentmods.dev/badge/skills/gerard-labs/superpowers-api-platform/functional-tests.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.00171 | $0.00636 |
| Opus 5.5 | $0.00068 | $0.00254 |
| Sonnet 5.5 | $0.00034 | $0.00127 |
| Haiku 4.5 | $0.00017 | $0.00064 |
Grade A, and why
functional-tests 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
Functional tests (Symfony — non-API)
Use when
- Writing functional tests for server-rendered controllers (Twig pages, form submissions, admin areas).
- Converting a bug report into a failing test (RED-GREEN-REFACTOR).
- Exercising authentication flows (login form, redirects, access-denied).
- Asserting form validation errors, CSRF, redirects, flash messages.
For REST / JSON-LD endpoints exposed by API Platform, use
gerard:api-platform-testsinstead — it coversApiTestCase, schema assertions, JSON-LD pagination shape, JWT clients, etc.
Default workflow
- RED: write a failing functional test that captures the target behavior.
- GREEN: implement the smallest controller / form change that makes the test green.
- REFACTOR: clean up controller and template while the test stays green.
- Broaden coverage to authorization (anonymous / forbidden / authorized) and error paths.
Guardrails
- Assert observable behavior, not internal state. Status codes, redirects, rendered content, flash messages — not service internals.
- Deterministic fixtures. Foundry factories or
ResetDatabase/ DAMA transaction rollback per test. - No order coupling. Each test starts from a clean state.
- CSRF on by default. If a form omits CSRF in the test, the test should fail.
- Real templates render — don't mock the renderer in functional tests; the goal is the full HTTP stack.
Progressive disclosure
SKILL.mdcovers posture and rules.reference.mdcarries the full patterns: WebTestCase skeleton, login helpers, form submission, redirect assertions, flash messages, CSRF, DAMA setup, scenario-based naming, ParaTest invocation.
Output contract
- A
tests/Functional/<Area>/<Feature>Test.phpextendingWebTestCase. - Tests covering happy path + anonymous + forbidden + invalid form paths.
- DAMA / ResetDatabase guarantees test isolation.
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.
- 1mo ago First seen · 47 lines · 171 tokens per session scan A 086c9f74da1e
functional-tests is a skill published in the GitHub repository gerard-labs/superpowers-api-platform (2 stars, last pushed 5mo ago), licensed MIT. It adds 171 tokens to every session and 636 once invoked, about $0.0007 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
write-tests
Add or update PHPUnit tests using this repository's E2E, functional, integration, and unit test conventions.
e2e-panther-playwright
Write end-to-end tests with Symfony Panther 2.4 for browser automation or Playwright for complex scenarios.
functional-tests
Write functional tests for Symfony controllers and HTTP endpoints using WebTestCase, getContainer, loginUser, and DAMA rollback.
mirrord-chaos
Help users chaos test their app with mirrord: inject artificial latency or connection errors into a mirrord session's outgoing traffic via per-session chaos rules managed with the mirrord chaos CLI. Use when a user wants to add latency or delay to outgoing connections or a dependency (e.g. a slow database), simulate…
test-native-extension
Validate a third-party control repo across four automated layers plus one printed manual recipe. Layer 1 asserts native-source structure (Android getName() and iOS +moduleName to manifest nativeModule; @ReactMethod / RCTEXPORTMETHOD to methods; no @ReactModule) plus load/init readiness (ReactPackage public no-arg…
test-site
Tests a deployed, activated Power Pages site at runtime using browser-based navigation, page crawling, and API request verification via Playwright. Use when the user wants to test, verify, or smoke-test their deployed site.