api-contract-sync

api-contract-sync is a skill for Claude Code from RaNDoM6913/claude-code-superkit. It costs 39 tokens per session (1,992 once invoked), scanned A, original, MIT.

A checker that compares an API description in OpenAPI or Swagger format with the routes and request or response code in a project.

In plain words
What is it for?
Use it after changing routes, handlers, data fields, or the OpenAPI/Swagger files to find mismatches.
Why use it?
It helps catch cases where the published API documentation no longer matches what the server actually accepts or returns.

Skill for Claude Code

Written for Claude Code: user-invocable in frontmatter. Also seen: mentions AGENTS.md.

Good fit Use it after changing routes, handlers, data fields, or the OpenAPI/Swagger files to find mismatches.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/random6913/claude-code-superkit/api-contract-sync
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 RaNDoM6913/claude-code-superkit --skill api-contract-sync
Clone the repo
git clone --depth 1 https://github.com/RaNDoM6913/claude-code-superkit

Made for: Claude Code.

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-contract-sync

README.md
[![agentmods](https://agentmods.dev/badge/skills/random6913/claude-code-superkit/api-contract-sync/github.svg)](https://agentmods.dev/skills/random6913/claude-code-superkit/api-contract-sync)
Your own site
<a href="https://agentmods.dev/skills/random6913/claude-code-superkit/api-contract-sync"><img src="https://agentmods.dev/badge/skills/random6913/claude-code-superkit/api-contract-sync/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-contract-sync

Your own site · 80×15
<a href="https://agentmods.dev/skills/random6913/claude-code-superkit/api-contract-sync"><img src="https://agentmods.dev/badge/skills/random6913/claude-code-superkit/api-contract-sync.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 1,992 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.
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.01992
Opus 5.5 $0.00016 $0.00797
Sonnet 5.5 $0.00008 $0.00398
Haiku 4.5 $0.00004 $0.00199

Measured today against content hash f213fe78a1cc, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

api-contract-sync 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 today.

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.

packages/codex/skills/api-contract-sync/SKILL.md · 97 lines

How it starts

The opening of the file, as written. The whole thing — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.

API Contract Sync

Review whether the API contract matches its implementation for the declared scope. Use for selected route, handler, DTO/schema, or specification changes and requested API audits. A code-level comparison does not establish deployed behavior. The role name does not authorize editing either side to make them agree.

Scope, context, and authority

Read applicable AGENTS.md first, then the relevant API/documentation map and project conventions. Establish the requested base/head, working-tree diff, or explicit API/version scope. Identify the authoritative specification, generated sources/artifacts, route registrations, handler/DTO code, and expected target configuration. Resolve ambiguous scope or conflicting sources before claiming complete coverage.

Review only. Propose corrections to the appropriate source owner; do not edit code/specs, regenerate tracked files, post comments, or call credentialed/live endpoints without task authority. Do not infer access from a URL, connection string, or installed client. Use safe local checks only within scope and existing authority; importing an app or running a spec generator can start services or write files, so inspect its behavior first. Redact secrets and private payloads.

Honor explicit task/project routing and acceptance ownership. Disclose INDEPENDENT versus INLINE SELF-REVIEW. Keep requested/configured model and effort separate from runtime-observed values with evidence or UNVERIFIED. Identity reporting alone adds no acceptance gate; an explicitly required independent/Astra gate still applies.

Discover the actual contract sources

Use the project's map rather than selecting the first file named openapi.yaml. Relevant sources may include OpenAPI/Swagger YAML/JSON, generated artifacts, annotations, schema modules, or a versioned external contract supplied by the user. Confirm the declared OpenAPI/Swagger version before interpreting schema semantics, references, and nullability. Do not fetch remote references without authorized access; unresolved $ref content remains unverified.

Read the full file on GitHub · 97 lines

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. today Changed · +14 lines · +22 tokens per session f213fe78a1cc
  2. 1mo ago First seen · 83 lines · 17 tokens per session scan A dd02f353d6e8

Subscribe to this mod's changes

api-contract-sync is a skill published in the GitHub repository RaNDoM6913/claude-code-superkit (3 stars, last pushed today), licensed MIT. It adds 39 tokens to every session and 1,992 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-31.

Related

Other skills, from other repositories