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-serializationnpx skills add gerard-labs/superpowers-api-platform --skill api-platform-serializationgit 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.00170 | $0.00685 |
| Opus 5 | $0.00085 | $0.00342 |
| Sonnet 5 | $0.00034 | $0.00137 |
| Haiku 4.5 | $0.00017 | $0.00068 |
Grade A, and why
api-platform-serialization 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.
What it actually says
API Platform 4.3 — Serialization
Use when
- Adding
#[Groups]to a resource or DTO. - Forcing relations to serialize as IRIs (or, exceptionally, embedded).
- Calculating fields without polluting the entity (custom normalizer).
- Adding admin-only or owner-only fields with a dynamic group.
- Tuning per-property date format / context with
#[Context].
Default workflow
- Define the read vs write groups (
product:list,product:read,product:create,product:update). - Apply
#[Groups]on every exposed property with a deliberate scope. - Force IRI on relations with
#[ApiProperty(readableLink: false, writableLink: false)]unless embedding is explicitly required. - Add
MaxDepth+enable_max_depth: trueon circular relations. - For computed / role-dependent fields, decide: Context Builder (runtime), Mutator (build-time), or custom Normalizer.
Guardrails
- One group per direction. Never reuse
product:readfor writes. - Sensitive fields out of every group. Use
#[Ignore]for passwords, tokens, reset codes. BackedEnumfor statuses. Never freestring.hydra_prefix: falseis the 4.x default — tests and clients consumemember,totalItems, etc. without thehydra:prefix.skip_null_values: trueis the 4.x default — no more"field": nullin responses.
Progressive disclosure
SKILL.mdcovers posture and decision tree.reference.mdcarries the full patterns: groups, MaxDepth, IRI forcing, BackedEnum,#[Context], custom Normalizer (ALREADY_CALLED pattern), conditional normalizer (Security-aware), Context Builder vs Mutator,gen_id, name converter,getValues()trick.
Output contract
- Resource / DTO with explicit per-property groups.
- Relations either IRI-only or embedded with a documented reason.
- Tests asserting the exact shape of the JSON-LD response.
- No
nullproperties leaking in the response (verifyskip_null_values).
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.
- 2d ago First seen · 48 lines · 0 tokens per session scan A 61b503aa5866
api-platform-serialization is a skill published in the GitHub repository gerard-labs/superpowers-api-platform (2 stars, last pushed 3mo ago), licensed MIT. It adds 170 tokens to every session and 685 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.