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 agentmods add skills/gerard-labs/superpowers-api-platform/api-platform-testsnpx skills add gerard-labs/superpowers-api-platform --skill api-platform-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/api-platform-tests)<a href="https://agentmods.dev/skills/gerard-labs/superpowers-api-platform/api-platform-tests"><img src="https://agentmods.dev/badge/skills/gerard-labs/superpowers-api-platform/api-platform-tests.svg" alt="Measured on agentmods" 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 | $0.00257 | $0.00788 |
| Opus 5 | $0.00129 | $0.00394 |
| Sonnet 5 | $0.00051 | $0.00158 |
| Haiku 4.5 | $0.00026 | $0.00079 |
Grade A, and why
api-platform-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 3d 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
API Platform 4.3 — Functional tests
Use when
- Writing API tests for a new resource / operation.
- Updating older tests still using
hydra:member/hydra:totalItems(broken in 4.x). - Speeding up a slow suite (Foundry → DAMA → ParaTest progression).
- Authenticating clients with JWT for protected endpoints.
- Asserting the JSON-LD schema strictly.
Default workflow
- Install the dev stack —
symfony/test-pack,http-client,browser-kit,justinrainbow/json-schema,dama/doctrine-test-bundle,zenstruck/foundry,brianium/paratest. - Wire DAMA via the PHPUnit extension; configure md5 hashing in
config/packages/test/security.yaml. - Write tests extending
ApiTestCasewithFactories+ResetDatabasetraits. - Cover happy path, 401, 403, 404, 422, ownership, filters, pagination on every operation.
- Run with
./vendor/bin/paratest -p8in CI for parallel execution.
Guardrails
- No
hydra:prefix anywhere in assertions in 4.x. Usemember,totalItems,view,next. - Default page size is 30 in 4.x (not 20 like 3.x). Adapt counts.
- Hash algorithm
md5is for tests only. Never in any other env. - One assertion per scenario. No conditional logic in tests.
- Tests are independent — DAMA transaction rollback or Foundry
ResetDatabaseensures it; never rely on order.
Progressive disclosure
SKILL.mdlists posture and rules.reference.mdcarries the full stack setup, the reusable authenticated client, JWT auth tests, schema assertions, filters + pagination + auth + ownership coverage matrix, scenario-based naming, CI patterns.
Output contract
- Tests in
tests/Functional/Api/extendingApiTestCase(or a project-specificAbstractApiTest). - Each operation covered with happy path + at least one negative case (401/403/404/422).
- Schema assertions on collection and item responses.
- CI invokes
./vendor/bin/paratest -p8.
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.
- 3d ago First seen · 48 lines · 257 tokens per session scan A a53dda17721c
api-platform-tests is a skill published in the GitHub repository gerard-labs/superpowers-api-platform (2 stars, last pushed 3mo ago), licensed MIT. It adds 257 tokens to every session and 788 once invoked, about $0.0013 per session on Opus 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 skills, from other repositories
api-integrations
Expose external APIs to Falcon Foundry via OpenAPI specs. TRIGGER when user asks to "create an API integration", "adapt an OpenAPI spec for Foundry", "expose an API to workflows", "connect to a third-party API", or runs foundry api-integrations create. Also trigger when user has an OpenAPI/Swagger spec and wants it…
symfony:doctrine-events
React to Doctrine entity lifecycle in Symfony with attribute listeners (#[AsDoctrineListener]/#[AsEntityListener], ORM 3) and lifecycle callbacks.
symfony:api-platform-dto-resources
Map entities to API DTOs in API Platform v4 with the Symfony Object Mapper (#[Map], stateOptions) for decoupled input/output contracts.
symfony:api-platform-filters
Implement API Platform filters - v4 Parameters API (QueryParameter) and legacy.
symfony:api-platform-versioning
Evolve API Platform APIs via deprecation (deprecationReason/sunset, RFC 8594/9745), the recommended alternative to versioning; plus path/header strategies.
symfony:bootstrap-check
Verify Symfony project configuration including .env, services.yaml, doctrine settings, and framework requirements.