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-upgradenpx skills add gerard-labs/superpowers-api-platform --skill api-platform-upgradegit clone --depth 1 https://github.com/gerard-labs/superpowers-api-platformWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/gerard-labs/superpowers-api-platform/api-platform-upgrade)<a href="https://agentmods.dev/skills/gerard-labs/superpowers-api-platform/api-platform-upgrade"><img src="https://agentmods.dev/badge/skills/gerard-labs/superpowers-api-platform/api-platform-upgrade.svg" alt="Measured on agentmods" height="20"></a>What 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.00049 | $0.00963 |
| Opus 5 | $0.00024 | $0.00481 |
| Sonnet 5 | $0.00010 | $0.00193 |
| Haiku 4.5 | $0.00005 | $0.00096 |
Grade A, and why
api-platform-upgrade 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 4d 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 — Upgrade Guide (3.x → 4.x → v5 prep)
Use when
- A
composer.lockanalysis (session hook) shows API Platform < 4.3. - Reviewing or migrating code that still imports
ApiPlatform\Core\, uses#[ApiFilter],openapiContext, or implementsSerializerAwareProviderInterface/SerializableProvider. - Bulk-renaming filters from the legacy classes to the modern 4.3 equivalents.
- Planning the v5 cut-over (preventing regressions via PHPStan / Deptrac).
Default workflow
- Determine the starting version from
composer.lock. Hard-stop on 3.x without explicit planning. - Apply the 3.x → 4.0 macro-changes (namespaces, package split, Providers/Processors, defaults).
- Apply the 4.0 → 4.2 changes (modern filter pattern using
parameters: [QueryParameter]). - Apply the 4.2 → 4.3 breaks (explicit
propertyon Exact/Iri/Partial/Uuid filters; review readonly entities; check@typeconsumers). - Run the Rector script for
openapiContextand inspect for any remaining legacy references. - Enable v5-prep guards (PHPStan rule, Deptrac layer) to prevent regressions.
Guardrails
- Do not migrate without a passing test suite. Re-baseline tests if they assert
hydra:member(replace bymember). - Default flips in 4.x can break consumers:
hydra_prefix:false,standard_put:true,rfc_7807_compliant_errors:true,pagination_items_per_page:30. Audit clients before flipping. eager_loading.force_eager: trueis the 4.x default but often counter-productive — set it tofalseand use targeted join fetches.- Only this skill is allowed to mention
#[ApiFilter],openapiContext,hydra:member,extends AbstractFilter, etc. The lint script rejects them elsewhere.
Progressive disclosure
SKILL.mdsummarizes the migration path.reference.mdcarries the full tables: 3.x → 4.0 macro changes, 4.0 → 4.2 filter shift, 4.2 → 4.3 breaks, behavioral changes (isGranted pre-provider, Hydra#ShortName, LDP headers), 4.3 novelties, removed-in-v5 list, full legacy → modern mapping, tooling (Rector, PHPStan rule, Deptrac),composer outdatedaudit.
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.
- 4d ago First seen · 51 lines · 49 tokens per session scan A de7dd6dc67a1
api-platform-upgrade is a skill published in the GitHub repository gerard-labs/superpowers-api-platform (2 stars, last pushed 3mo ago), licensed MIT. It adds 49 tokens to every session and 963 once invoked, about $0.0002 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
api-integrations
Expose external APIs to Falcon Foundry via OpenAPI specs. TRIGGER when user asks to "create an API integration", "adapt an OpenAPI spec for Foundry", "expose an API to workflows", "connect to a third-party API", or runs foundry api-integrations create. Also trigger when user has an OpenAPI/Swagger spec and wants it…
symfony:doctrine-events
React to Doctrine entity lifecycle in Symfony with attribute listeners (#[AsDoctrineListener]/#[AsEntityListener], ORM 3) and lifecycle callbacks.
symfony:api-platform-dto-resources
Map entities to API DTOs in API Platform v4 with the Symfony Object Mapper (#[Map], stateOptions) for decoupled input/output contracts.
symfony:api-platform-filters
Implement API Platform filters - v4 Parameters API (QueryParameter) and legacy.
symfony:api-platform-versioning
Evolve API Platform APIs via deprecation (deprecationReason/sunset, RFC 8594/9745), the recommended alternative to versioning; plus path/header strategies.
symfony:bootstrap-check
Verify Symfony project configuration including .env, services.yaml, doctrine settings, and framework requirements.