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-performancenpx skills add gerard-labs/superpowers-api-platform --skill api-platform-performancegit 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.00237 | $0.00777 |
| Opus 5 | $0.00118 | $0.00388 |
| Sonnet 5 | $0.00047 | $0.00155 |
| Haiku 4.5 | $0.00024 | $0.00078 |
Grade A, and why
api-platform-performance 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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
API Platform 4.3 — Performance
Use when
- The API is slower than expected, especially on list endpoints.
- A
max_joins: 30exception fires because the entity has many relations. - Memory blows up on large collections.
- p99 latency is above ~50 ms for simple routes.
- Cache invalidation cannot keep up with writes.
Default workflow
- Detect the
force_eager: truetrap. Switch tofalseand replace with targeted join fetches in repositories. - Profile with the Symfony profiler in dev — look for N+1 patterns.
- For list views: project a DTO via DQL
NEW App\Dto\PostListItem(...)instead of hydrating the full entity. - Enable APCu for resource metadata cache in prod.
- Adopt FrankenPHP worker mode for high-traffic APIs (stateful kernel between requests).
- Add HTTP cache headers per operation and
cacheTagsfor invalidation.
Guardrails
force_eager: trueis the 4.x default but rarely what you want for an entity with many relations. Set it tofalseand use targetedaddSelect()join fetches per query.#[ApiProperty(fetchEager: true)]for specific fields only — never blanket eager loading.- Never iterate without
clear()on million-row collections — memory will explode. - HTTP cache + write paths must agree on invalidation — purge
cacheTagson every write. - FrankenPHP worker mode requires worker-safe code (no static state leaks).
Progressive disclosure
SKILL.mdcovers posture and rules.reference.mdcarries the full patterns: fetch modes, eager loading trap, join fetch recipe, DTO projection, batch iteration, HINT_READ_ONLY, APCu metadata cache, FrankenPHP worker, HTTP cache headers, cache tags + Varnish PURGE, dynamic Last-Modified listener.
Output contract
eager_loading.force_eager: falseconfirmed (or documented exception).- Repository methods using targeted
addSelect()for list endpoints. - DTO projections via DQL
NEWfor large lists. - APCu metadata cache configured in prod.
- HTTP cache configured per operation (where applicable).
cacheTagspurged on writes.- p99 latency measured before/after.
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 · 52 lines · 0 tokens per session scan A 4f46e535c21d
api-platform-performance is a skill published in the GitHub repository gerard-labs/superpowers-api-platform (2 stars, last pushed 3mo ago), licensed MIT. It adds 237 tokens to every session and 777 once invoked, about $0.0012 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
horse-database-pooling
Guide for setting up thread-safe database connection pooling (FireDAC / UniDAC) in multithreaded Horse applications.
db-infra-mocks
Propose minimal seams and local substitutes so tests run without real RDBMS/Redis/Mongo infrastructure.
migration-helper
Analyze GORM model changes, estimate resulting schema (DDL) differences, and propose safe migration steps with verification guidance.
npgsqlrest
Build and modify REST APIs with NpgsqlRest — exposing PostgreSQL as HTTP endpoints from two sources (database functions/procedures/tables/views, and plain .sql files), driven by SQL comment annotations (no C# needed). Use when working in an NpgsqlRest project: writing or changing endpoint SQL (functions or .sql…
creating-database-migrations
Use when adding or editing Nango database migrations - covers migration directory selection, timestamped .cjs naming, matching recent migration style, down migration decisions, and foreign key ON DELETE conventions.
backend-dev-agent
后端开发 Agent — API 设计、数据库优化、服务器端逻辑、认证授权、性能优化.