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/juanmhidalgo/claude-plugins/api-change-documentationnpx skills add juanmhidalgo/claude-plugins --skill api-change-documentationgit clone --depth 1 https://github.com/juanmhidalgo/claude-pluginsWrote 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/juanmhidalgo/claude-plugins/api-change-documentation)<a href="https://agentmods.dev/skills/juanmhidalgo/claude-plugins/api-change-documentation"><img src="https://agentmods.dev/badge/skills/juanmhidalgo/claude-plugins/api-change-documentation.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.00036 | $0.00628 |
| Opus 5 | $0.00018 | $0.00314 |
| Sonnet 5 | $0.00007 | $0.00126 |
| Haiku 4.5 | $0.00004 | $0.00063 |
Grade A, and why
api-change-documentation 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 yesterday.
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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
API Cross-Team Handoff Guidelines
This skill provides the specific output formats and classification rules for generating handoff prompts between frontend and backend teams.
Breaking Change Classification
Use this classification when generating handoff prompts:
| Change Type | Breaking? | Action Required |
|---|---|---|
| Remove response field | YES | Migration guide required |
| Change field type | YES | Migration guide required |
| Rename field | YES | Migration guide required |
| Change endpoint path/method | YES | Migration guide required |
| Add required request param | YES | Migration guide required |
| Add optional response field | NO | Document only |
| Add optional query param | NO | Document only |
| Add new endpoint | NO | Document only |
| Deprecate (not remove) field | NO | Document with timeline |
Schema Output Formats
For Frontend Handoffs (TypeScript)
interface Example {
id: string;
name: string | null; // null = field present, value absent
role: 'admin' | 'user'; // union for enums
metadata?: Record<string, unknown>; // ? = field may be omitted
}
For Backend Handoffs (Language-Agnostic)
{
"id": "string (UUID v4)",
"count": "integer (min: 0, max: 1000)",
"status": "enum: pending | active | completed",
"config": {
"enabled": "boolean (default: true)"
}
}
Handoff Checklists
Backend → Frontend
- All changed endpoints listed with HTTP method
- TypeScript interfaces for all affected types
- Breaking changes marked with migration steps
- New error scenarios with status codes
- Before/after payload examples
Frontend → Backend
- UI/UX context explaining the need
- Request/response schemas (language-agnostic)
- Validation requirements
- Error scenarios to handle
- Performance expectations (call frequency, data volume)
Edge Cases to Always Document
- Null vs omission:
field: nullvs field not present - Empty arrays:
[]vsnullvs omitted - Pagination: zero/one-based, default size, cursor vs offset
- Timestamps: ISO 8601, timezone, precision
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.
- yesterday First seen · 89 lines · 36 tokens per session scan A 9e9c3cce8591
api-change-documentation is a skill published in the GitHub repository juanmhidalgo/claude-plugins (8 stars, last pushed 10d ago), licensed MIT. It adds 36 tokens to every session and 628 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-09-03.
Other skills, from other repositories
design-import
Scaffolds React components from a Claude Design handoff bundle and stops at files on disk: no stories, no tests, no pull request. Use when handed a claude.ai/design URL or a local bundle file; when that same scaffold should carry on through test generation, browser verification and an opened PR, run /ork:design-ship…
chakra-ui-builder
Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…
material-ui-tailwind
Integrates Material UI with Tailwind CSS v4 using cascade layers (enableCssLayer, @layer order) and documents Tailwind v3 interoperability (preflight, important, injectFirst, portals). Use when combining MUI with Tailwind utilities, slotProps className, or theme token bridges.
verify
Use when you want to validate changes before committing, or when you need to check all React contribution requirements.
extract-errors
Use when adding new error messages to React, or seeing "unknown error code" warnings.
r3f-best-practices
React Three Fiber (R3F) and Poimandres ecosystem best practices. Use when writing, reviewing, or optimizing R3F code. Triggers on tasks involving @react-three/fiber, @react-three/drei, zustand, @react-three/postprocessing, @react-three/rapier, or leva.