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 api-platform-testsgit 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/api-platform-tests)<a href="https://agentmods.dev/skills/dev-toolings/superpowers-symfony/api-platform-tests"><img src="https://agentmods.dev/badge/skills/dev-toolings/superpowers-symfony/api-platform-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/dev-toolings/superpowers-symfony/api-platform-tests"><img src="https://agentmods.dev/badge/skills/dev-toolings/superpowers-symfony/api-platform-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.00025 | $0.00510 |
| Opus 5.5 | $0.00010 | $0.00204 |
| Sonnet 5.5 | $0.00005 | $0.00102 |
| Haiku 4.5 | $0.00003 | $0.00051 |
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 17d 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.
This is a copy
88% identical to api-platform-dto-resources — 42 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Api Platform Tests (Symfony)
Use when
- Writing functional tests for API Platform endpoints: collection, item, create, update, delete.
- Asserting validation errors (422) and access control (401, 403).
- Checking filters, pagination, or the JSON schema of responses.
- Setting up a clean database and test data for API tests.
Default workflow
- Extend
ApiTestCaseand seed data with Foundry factories (createOne,createMany). - Reset state with
#[ResetDatabase]and theFactoriestrait, with DAMA rolling back each test. - Call
static::createClient()->request()and assert the status code, content type, andassertJsonContains(). - Authenticate with
auth_bearerand cover the anonymous, owner, and other-user cases. - Assert
memberandtotalItemsfor filters and pagination (hydra:-prefixed only withhydra_prefix: true). - Assert the shape with
assertMatchesResourceItemJsonSchema()andassertMatchesResourceCollectionJsonSchema().
Guardrails
- Send
PATCHwith theapplication/merge-patch+jsoncontent type. #[ResetDatabase]needs PHPUnit 10+ and Foundry 2.9: use theResetDatabasetrait on PHPUnit 9.- Cover the failure paths too: 404, 422, 401, 403. A type error on a constrained property is 422 in 5.0 but 400 in 4.4 and earlier.
- Read the configured items per page rather than hardcoding a page size in assertions.
Progressive disclosure
- Use this file for execution posture and risk controls.
- Open references when deep implementation details are needed.
Output contract
- The test classes added and the endpoints they cover.
- Factories and reset strategy used.
- Test run output, including the failure paths.
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.
- 17d ago Changed · +4 lines c870137d30db
- 1mo ago Changed · +2 lines · -3 tokens per session bfdb16ec6e99
- 1mo ago First seen · 43 lines · 28 tokens per session scan A 1efa5d71a7d4
api-platform-tests is a skill published in the GitHub repository dev-toolings/superpowers-symfony (226 stars, last pushed 17d ago), licensed MIT. It adds 25 tokens to every session and 510 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 88% identical to api-platform-dto-resources, differing in 42 lines, and is treated as a copy.
Other skills, from other repositories
hermit-scribe
File a GitHub issue or post a comment on an existing issue via a GitHub App bot identity. Use when the operator says "file as a GH issue", "open an issue for PROP-NNN", "report this to the tracker", "add a comment to issue.
test-run
Run plugin test suites in this monorepo and report a concise pass/fail summary. Optional plugin slug arg; without arg, runs all plugins under plugins/.
proof-e2e
Build E2E test specs for critical user journeys — Playwright or Cypress, page objects, setup/teardown, CI config. Use when asked to "write E2E tests", "end-to-end testing", "browser tests", "UI tests", or "Playwright tests".
mean-tester
Mean test another agent when someone asks you to test, check or break it. Invoke on "test @agent", "mean test @agent", "check whether @agent works", on "continue " or "rerun " in a new message, or on "continue" in a thread where you already reported a campaign, and on "Judge this recorded exchange".
proof-strategy
Produce a test strategy for a project or feature — risk map, test type decisions, coverage targets, CI config. Use when asked to "create test strategy", "what should we test", "testing plan", or "improve test coverage".
implement
Implement a ticket or feature with proportional planning, test first behavior changes, independent review when available, and verification through the real affected surface.