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-versioningnpx skills add gerard-labs/superpowers-api-platform --skill api-platform-versioninggit 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.00179 | $0.00680 |
| Opus 5 | $0.00089 | $0.00340 |
| Sonnet 5 | $0.00036 | $0.00136 |
| Haiku 4.5 | $0.00018 | $0.00068 |
Grade A, and why
api-platform-versioning 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 — Versioning
Use when
- Adding a new operation or resource that breaks the contract.
- Carving out a
/v2/set of endpoints next to/v1/. - Marking an operation deprecated with a Sunset date.
- Migrating older code that still uses
openapiContext: ['deprecated' => true](deprecated 4.x) to the modern attribute.
Default workflow
- Decide the strategy — URI versioning (breaking), Output DTOs per version (when payload shape diverges), header-based, or group additive (minor additions only).
- Implement the chosen strategy with explicit
uriTemplate, dedicated DTOs / Provider, or new group. - On retired operations: set
deprecationReason,sunset, andopenapi: new Model\Operation(deprecated: true). - Add a
KernelEvents::RESPONSEsubscriber to emitSunset/Deprecation/Link: …; rel="successor-version"headers. - Document the diff at the top of each new DTO (changelog comment).
Guardrails
- URI versioning for breaking changes. Clearest signal for clients.
- Group additive only for additions — never to remove or rename.
- Always announce a sunset date when retiring an operation.
- Limit active versions — keep 2-3 at most. Beyond that, the maintenance burden explodes.
- Test every active version — no silent regression on v1.
Progressive disclosure
SKILL.mdlists strategies and rules.reference.mdcarries full examples for each strategy, theopenapi4.x attribute (Rector migration script foropenapiContext), Sunset / Deprecation / Link headers, the DTO changelog header, multi-version functional tests, and best practices.
Output contract
- New resources / DTOs / Providers per version with explicit
uriTemplate. - Deprecated operations carry
deprecationReason,sunset, andopenapi: new Model\Operation(deprecated: true). - A response subscriber emits Sunset headers.
- Functional tests cover every active version.
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 · 47 lines · 0 tokens per session scan A 1a5f4075e84f
api-platform-versioning is a skill published in the GitHub repository gerard-labs/superpowers-api-platform (2 stars, last pushed 3mo ago), licensed MIT. It adds 179 tokens to every session and 680 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.