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-resourcesnpx skills add gerard-labs/superpowers-api-platform --skill api-platform-resourcesgit clone --depth 1 https://github.com/gerard-labs/superpowers-api-platformWhat 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.00132 | $0.00584 |
| Opus 5 | $0.00066 | $0.00292 |
| Sonnet 5 | $0.00026 | $0.00117 |
| Haiku 4.5 | $0.00013 | $0.00058 |
Grade A, and why
api-platform-resources 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 — Resources & operations
Use when
- Designing a new
#[ApiResource]or evolving an existing one. - Choosing which operations to expose and how to scope them.
- Modeling subresources (orders under a customer, items under an order).
- Forcing the IRI-only rule on relations.
Default workflow
- Define the operation boundary — which payload, which invariants, which actor.
- Declare the operations explicitly (
new Get(...),new Post(...), etc.) with per-operation groups, security, validation. - Apply the Resource-First principle — keep the Resource decoupled from the Entity unless they are genuinely identical.
- Validate the contract end-to-end (
debug:router,api:openapi:export, functional tests).
Guardrails
- Resource ≠ Entity. The Resource is the external contract; do not let it leak Doctrine specifics.
- IRI-only on relations: never accept a scalar
int $customerId, always aCustomer $customerthat API Platform resolves from/api/customers/.... - No
use_symfony_listeners: trueunless you really need a Symfony controller — the providers/processors path is preferred. - No magic operations: declare each one.
paginationItemsPerPagedefault is 30 in 4.x (not 20).
Progressive disclosure
SKILL.mdcovers posture and decisions.reference.mdcarries the full 4.3 patterns: subresources withLink,itemUriTemplate, content negotiation, anti-patterns, legacy controllers (to avoid).
Output contract
- Updated
#[ApiResource]attributes with explicit operations and contexts. - Justification for IRI-only (or, exceptionally, embedded) choices.
- Functional test coverage on each operation, including 404 / 401 / 403 / 422.
- Generated routes confirmed via
php bin/console debug:router | grep api.
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 · 45 lines · 132 tokens per session scan A 70cf102803f7
api-platform-resources is a skill published in the GitHub repository gerard-labs/superpowers-api-platform (2 stars, last pushed 3mo ago), licensed MIT. It adds 132 tokens to every session and 584 once invoked, about $0.0007 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
server-setup
Initialize tRPC with initTRPC.create(), define routers with t.router(), create procedures with .query()/.mutation()/.subscription(), configure context with createContext(), export AppRouter type, merge routers with t.mergeRouters(), lazy-load routers with lazy().
client-setup
Create a vanilla tRPC client with createTRPCClient (), configure link chain with httpBatchLink/httpLink, dynamic headers for auth, transformer on links (not client constructor). Infer types with inferRouterInputs and inferRouterOutputs. AbortController signal support. TRPCClientError typing.
non-json-content-types
Handle FormData, file uploads, Blob, Uint8Array, and ReadableStream inputs in tRPC mutations. Use octetInputParser from @trpc/server/http for binary data. Route non-JSON requests with splitLink and isNonJsonSerializable() from @trpc/client. FormData and binary inputs only work with mutations (POST).
caching
Set HTTP cache headers on tRPC query responses via responseMeta callback for CDN and browser caching. Configure Cache-Control, s-maxage, stale-while-revalidate. Handle caching with batching and authenticated requests. Avoid caching mutations, errors, and authenticated responses.
portaljs-connect-ckan
Wire a scaffolded PortalJS portal to a CKAN backend over its API. Generates a tiny server-side fetch client (no runtime dependency) and feeds the /search catalog and /@namespace/slug showcases from CKAN instead of datasets.json. Use when connecting an existing portal to a live CKAN instance instead of a static…
horse-grpc
Guidelines and workflows for developing and maintaining gRPC services, HTTP/2 h2c transport, and Protobuf serialization within the Horse framework.