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-identifiersnpx skills add gerard-labs/superpowers-api-platform --skill api-platform-identifiersgit 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.00148 | $0.00710 |
| Opus 5 | $0.00074 | $0.00355 |
| Sonnet 5 | $0.00030 | $0.00142 |
| Haiku 4.5 | $0.00015 | $0.00071 |
Grade A, and why
api-platform-identifiers 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 — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.
API Platform 4.3 — Identifiers (UUID v7, ULID, composite, custom)
Use when
- Designing a new resource: should the identifier be a sequential int, a UUID, a ULID, or a slug?
- Switching an existing resource from auto-increment to UUID v7 (anti-enumeration + cursor pagination).
- Modeling a composite identifier (
/customer/{customerId}/order/{orderId}). - Exposing a slug as the public identifier while keeping an internal numeric ID.
- Customizing how an identifier is parsed from the URI or rendered in the response.
Default workflow
- Default to UUID v7 (
Symfony\Component\Uid\Uuid::v7()) on public resources — chronologically sortable + non-enumerable. - Annotate the identifier with
#[ApiProperty(identifier: true)]and persist it as a nativeuuidcolumn (PostgreSQL) or as aulidcolumn. - For composite identifiers, declare them in
uriVariableswithLink(fromClass: …, identifiers: ['id']). - For custom identifiers (slug), set
#[ApiProperty(identifier: true)]on the slug and#[ApiProperty(identifier: false)]on the auto-incrementid. - Decorate
UriVariableTransformerInterfaceonly when the string-to-typed-object conversion is non-trivial.
Guardrails
- No sequential auto-increment IDs on public resources. Volume leakage + enumeration.
- UUID v7 > UUID v4 for any resource where chronological ordering helps (cursor pagination, B-tree indexing).
- Native DB column types:
uuid(PostgreSQL) instead ofvarchar(36)— better indexing, smaller storage. - Composite identifiers must be stable — never reuse a (customerId, orderId) pair.
Progressive disclosure
SKILL.mdcovers the decision tree.reference.mdcarries the full catalog (supported types), UUID v7 + cursor pagination wiring, composite identifiers withLink, custom slug pattern,UriVariableTransformerInterfaceandIdentifiersExtractorInterfacerecipes.
Output contract
- Public resources use UUID v7 / ULID / slug — no exposed auto-increment.
- Composite identifiers declared via
Link(uriVariables: …, identifiers: […]). - DB columns use native types where supported.
- Tests assert the IRI shape (UUID format, slug format) instead of integer matching.
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 3f2ee98391f5
api-platform-identifiers is a skill published in the GitHub repository gerard-labs/superpowers-api-platform (2 stars, last pushed 3mo ago), licensed MIT. It adds 148 tokens to every session and 710 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.