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-securitynpx skills add gerard-labs/superpowers-api-platform --skill api-platform-securitygit 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.00177 | $0.00748 |
| Opus 5 | $0.00088 | $0.00374 |
| Sonnet 5 | $0.00035 | $0.00150 |
| Haiku 4.5 | $0.00018 | $0.00075 |
Grade A, and why
api-platform-security 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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
API Platform 4.3 — Security
Use when
- Wiring
security/securityPostDenormalize/securityPostValidationon operations. - Writing or testing a voter (
POST_VIEW,POST_EDIT, etc.). - Filtering a collection by owner via a Doctrine extension.
- Setting up JWT authentication (Lexik) or OIDC.
- Configuring CORS for public / partner consumers.
- Switching identifiers to UUID v7 or ULID to remove enumeration risk.
Default workflow
- Apply
securityper operation. Fail closed — nosecurity:means public, only by design. - Decide between expression (simple) and Voter (complex). Cross more than one condition → Voter.
- For mutations that mutate ownership, use
securityPostDenormalizewithprevious_objectto enforce invariants. - For each sensitive property, decide: group split,
#[ApiProperty(security: ...)], or both. - Identifiers:
Uuid::v7()/Ulidon every public resource. No sequential IDs.
Guardrails
- Fail secure. Anything not explicitly public is
is_granted('ROLE_USER')minimum. securityMessageon every guarded operation — explicit feedback, no debug leakage.extraProperties: ['throw_on_access_denied' => true]— without it, an unauthorized field change is silently dropped instead of throwing 403.- Never log JWT contents. JWT is readable; no PII in claims.
- No
*in CORS whenallow_credentials: true. List the explicit origins. - Tests cover refusal AND acceptance. Both branches matter.
Progressive disclosure
SKILL.mdlists the posture and decision tree.reference.mdcarries the full patterns: operation security expressions, voters, query extensions, property security, UUID/ULID, JWT (Lexik) end-to-end (keys, security.yaml, Swagger UI, refresh tokens, storage), OIDC alternative, CORS configuration, performance note 4.3.
Output contract
- Each operation has an explicit
security(or a documented public exception). - Voters tested in isolation (
./vendor/bin/phpunit --filter=Voter). - Collection queries filtered through a
QueryCollectionExtensionInterface+QueryItemExtensionInterface. - Identifiers use UUID v7 / ULID where applicable.
- JWT / OIDC + CORS configurations match the published examples.
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.
- 2d ago First seen · 51 lines · 0 tokens per session scan A 8d1d0137d1e5
api-platform-security is a skill published in the GitHub repository gerard-labs/superpowers-api-platform (2 stars, last pushed 3mo ago), licensed MIT. It adds 177 tokens to every session and 748 once invoked, about $0.0009 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.