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-state-providersgit 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-state-providers)<a href="https://agentmods.dev/skills/dev-toolings/superpowers-symfony/api-platform-state-providers"><img src="https://agentmods.dev/badge/skills/dev-toolings/superpowers-symfony/api-platform-state-providers/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-state-providers"><img src="https://agentmods.dev/badge/skills/dev-toolings/superpowers-symfony/api-platform-state-providers.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.00044 | $0.00526 |
| Opus 5.5 | $0.00018 | $0.00210 |
| Sonnet 5.5 | $0.00009 | $0.00105 |
| Haiku 4.5 | $0.00004 | $0.00053 |
Grade A, and why
api-platform-state-providers 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
84% identical to api-platform-dto-resources — 39 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 State Providers (Symfony)
Use when
- Reading data from a source other than the default Doctrine provider.
- Wrapping the Doctrine provider to post-process results (return a DTO, enforce a tenant scope).
- Business logic must run before or after persisting (hashing, slug, dispatching a message).
- A v4 read endpoint must dispatch a query or command through a processor.
Default workflow
- Implement
ProviderInterface::provide()returningiterable|object|null, wherenullgives a 404 (v3.4 declaresmixed). - To keep Doctrine fetching, inject
api_platform.doctrine.orm.state.item_providerandapi_platform.doctrine.orm.state.collection_providerwith#[Autowire]. - Implement
ProcessorInterface::process()and delegate toapi_platform.doctrine.orm.state.persist_processororremove_processor. - Wire them with
provider:andprocessor:on the resource or the operation; autoconfiguration registers them, and theapi_platform.state_providerorapi_platform.state_processortag is only needed without it. - For a processor on
GETorGetCollection, addwrite: true(v4 only).
Guardrails
- Run pre-persist logic before calling the inner processor and side effects after it returns.
- A processor returns the created or modified object, and nothing for
DELETE. write: trueon safe methods is v4 only: v3.4 processors run on write methods only.DataProviderandDataPersisterare v2 interfaces and no longer exist.
Progressive disclosure
- Use this file for execution posture and risk controls.
- Open references when deep implementation details are needed.
Output contract
- The providers and processors added, and the operations they are wired to.
- Which built-in services are decorated.
- Tests for the not-found, success, and side-effect 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 · +3 lines · +12 tokens per session b7b36f610506
- 1mo ago Changed · +3 lines · -3 tokens per session f28c99175d9a
- 1mo ago First seen · 42 lines · 35 tokens per session scan A 4b657eb50880
api-platform-state-providers is a skill published in the GitHub repository dev-toolings/superpowers-symfony (226 stars, last pushed 17d ago), licensed MIT. It adds 44 tokens to every session and 526 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 84% identical to api-platform-dto-resources, differing in 39 lines, and is treated as a copy.
Other skills, from other repositories
spine-design
Produce a system design doc — components, data flow, decisions made, tradeoffs, failure modes. Not a list of options. An actual design with calls made. Use when asked for "system design for", "architect this", "how should we build", or "design the backend".
warden-harden
Produce a hardening spec and implement it — auth patterns, security headers, rate limiting, input validation, secrets management, dependency hygiene. Use when asked to "harden this", "add security to this service", "what security do I need", or "secure this before launch".
cortex-integrate
Design and implement an AI feature integration — model selection, architecture pattern, system prompt, data flow, error handling, cost estimate. Use when asked to "add AI to this", "LLM integration", "add Claude/GPT", or "AI-powered feature".
spine-api
Design and spec an API — endpoints, request/response shapes, error codes, auth pattern, pagination. Applies Stripe's consistency principles. Use when asked to "design an API", "build API endpoints", "create REST API", or "API for this feature".
spine-perf
Find and fix performance bottlenecks — N+1 queries, missing indexes, sync bottlenecks, caching gaps. Use when asked "why is this slow", "performance issue", "optimize this endpoint", or "N+1 queries".
spine-review
API and backend code review — REST conventions, auth, validation, error handling, pagination, rate limiting, test coverage. Use when asked to "review this API", "code review", "review backend", or "pre-launch backend check".