api-platform-versioning

api-platform-versioning is a skill for Claude Code from dev-toolings/superpowers-symfony. It costs 39 tokens per session (513 once invoked), scanned A, original, MIT.

A guide for changing APIs built with API Platform, a Symfony-based toolkit for exposing application data through web APIs. It favors deprecating old API behavior and documenting replacements instead of immediately creating separate versions.

In plain words
What is it for?
Use it to define API operations, update resources or data-transfer objects, configure providers and processors, and test successful and failing requests.
Why use it?
It helps keep API responses, validation, security, and documentation aligned as an API changes. It reduces accidental exposure of internal data and unclear contract changes.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the superpowers-symfony plugin — 44 skills, 13 commands, 7 agents, 1 hook shipped together

Good fit Use it to define API operations, update resources or data-transfer objects, configure providers and processors, and test successful and failing requests.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/dev-toolings/superpowers-symfony/api-platform-versioning
Install

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.

Any agent
npx skills add dev-toolings/superpowers-symfony --skill api-platform-versioning
Clone the repo
git clone --depth 1 https://github.com/dev-toolings/superpowers-symfony

Made for: Claude Code.

Or install superpowers-symfony, the plugin that ships this one along with the rest of its 44 skills, 13 commands, 7 agents, 1 hook.

Wrote 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.

agentmods badge for api-platform-versioning

README.md
[![agentmods](https://agentmods.dev/badge/skills/dev-toolings/superpowers-symfony/api-platform-versioning/github.svg)](https://agentmods.dev/skills/dev-toolings/superpowers-symfony/api-platform-versioning)
Your own site
<a href="https://agentmods.dev/skills/dev-toolings/superpowers-symfony/api-platform-versioning"><img src="https://agentmods.dev/badge/skills/dev-toolings/superpowers-symfony/api-platform-versioning/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for api-platform-versioning

Your own site · 80×15
<a href="https://agentmods.dev/skills/dev-toolings/superpowers-symfony/api-platform-versioning"><img src="https://agentmods.dev/badge/skills/dev-toolings/superpowers-symfony/api-platform-versioning.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 39 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 513 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00039 $0.00513
Opus 5.5 $0.00016 $0.00205
Sonnet 5.5 $0.00008 $0.00103
Haiku 4.5 $0.00004 $0.00051

Measured 16d ago against content hash 5549c1901f05, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 16d 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.

content/skills/api-platform-versioning/SKILL.md · 48 lines

What it actually says

Api Platform Versioning (Symfony)

Use when

  • A field, operation, or resource is being renamed or removed and consumers need time to migrate.
  • Announcing a removal date to clients with Sunset and Deprecation headers.
  • Deciding between deprecation and parallel /v1 and /v2 surfaces.
  • A breaking representation change that deprecation and groups cannot express.

Default workflow

  1. Try deprecation first: set deprecationReason on the resource, the operation, or #[ApiProperty].
  2. Add sunset: with a date, and on v4 add headers carrying Deprecation (RFC 9745) and a Link with rel="successor-version".
  3. Before v4, emit those headers from a KernelEvents::RESPONSE listener.
  4. Only if still breaking, expose parallel uriTemplate values (/v1, /v2) with distinct groups, or output DTOs with one provider per version.
  5. Mark the old operation as deprecated in OpenAPI, document the changes per version, and test every active version.

Guardrails

  • Prefer deprecation: path versioning is the fallback, not the default.
  • Always set a sunset date and keep at most 2 or 3 versions active.
  • deprecationReason and sunset are stable across v3 and v4, but the RFC 9745 headers option is v4-era: verify it on your installed version.
  • Use groups for minor additive changes rather than a new version.

Progressive disclosure

  • Use this file for execution posture and risk controls.
  • Open references when deep implementation details are needed.

Output contract

  • The deprecation or versioning strategy chosen and why.
  • Deprecated elements with their sunset dates and successor links.
  • Tests for each active version and for the headers.

References

  • reference.md
Files

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.

Changes

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.

  1. 16d ago Changed · +3 lines 5549c1901f05
  2. 1mo ago Changed · +2 lines · -3 tokens per session b8ed65c5a65b
  3. 1mo ago First seen · 43 lines · 42 tokens per session scan A 110b3af6291f

Subscribe to this mod's changes

api-platform-versioning is a skill published in the GitHub repository dev-toolings/superpowers-symfony (226 stars, last pushed 16d ago), licensed MIT. It adds 39 tokens to every session and 513 once invoked, about $0.0002 per session on Opus 5.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-30.

Related

Other skills, from other repositories

spine-design

Produce a system design doc — components, data flow, decisions made, tradeoffs, failure modes. Not a list of options. An actual design with calls made. Use when asked for "system design for", "architect this", "how should we build", or "design the backend".

tonone-ai/tonone · 62 tokens

warden-harden

Produce a hardening spec and implement it — auth patterns, security headers, rate limiting, input validation, secrets management, dependency hygiene. Use when asked to "harden this", "add security to this service", "what security do I need", or "secure this before launch".

tonone-ai/tonone · 61 tokens

cortex-integrate

Design and implement an AI feature integration — model selection, architecture pattern, system prompt, data flow, error handling, cost estimate. Use when asked to "add AI to this", "LLM integration", "add Claude/GPT", or "AI-powered feature".

tonone-ai/tonone · 58 tokens

spine-api

Design and spec an API — endpoints, request/response shapes, error codes, auth pattern, pagination. Applies Stripe's consistency principles. Use when asked to "design an API", "build API endpoints", "create REST API", or "API for this feature".

tonone-ai/tonone · 57 tokens

spine-review

API and backend code review — REST conventions, auth, validation, error handling, pagination, rate limiting, test coverage. Use when asked to "review this API", "code review", "review backend", or "pre-launch backend check".

tonone-ai/tonone · 52 tokens

spine-perf

Find and fix performance bottlenecks — N+1 queries, missing indexes, sync bottlenecks, caching gaps. Use when asked "why is this slow", "performance issue", "optimize this endpoint", or "N+1 queries".

tonone-ai/tonone · 55 tokens