agentmods.dev

openapi-doc-sync

openapi-doc-sync is a skill for Claude Code, Codex from Aibier/claude-em-toolkit. It costs 38 tokens per session (488 once invoked), scanned A, original, MIT.

A daily updater for API documentation written in the OpenAPI format, a standard way to describe web endpoints, their inputs, and their responses.

In plain words
What is it for?
Use it to add missing routes, update request and response details, flag endpoints that may need removal, and maintain a changelog.
Why use it?
It finds differences between the code and the API documentation, so new or changed endpoints are less likely to be missed. It also records changes and updates the documented version.

Skill for Claude CodeCodex

not rated 5 2mo ago A scan 38 tokens original MIT
View the source file Aibier/claude-em-toolkit
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.

agentmods
npx agentmods add skills/aibier/claude-em-toolkit/openapi-doc-sync
Any agent
npx skills add Aibier/claude-em-toolkit --skill openapi-doc-sync
Clone the repo
git clone --depth 1 https://github.com/Aibier/claude-em-toolkit

Made for: Claude Code, Codex.

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 openapi-doc-sync

README.md
[![agentmods](https://agentmods.dev/badge/skills/aibier/claude-em-toolkit/openapi-doc-sync.svg)](https://agentmods.dev/skills/aibier/claude-em-toolkit/openapi-doc-sync)
Your own site
<a href="https://agentmods.dev/skills/aibier/claude-em-toolkit/openapi-doc-sync"><img src="https://agentmods.dev/badge/skills/aibier/claude-em-toolkit/openapi-doc-sync.svg" alt="Measured on agentmods" height="20"></a>
Per session 38 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 488 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00038 $0.00488
Opus 5 $0.00019 $0.00244
Sonnet 5 $0.00008 $0.00098
Haiku 4.5 $0.00004 $0.00049

Measured 3d ago against content hash 9ef21fc6573f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

openapi-doc-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 3d 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.

.claude/skills/openapi-doc-sync/SKILL.md · 45 lines

What it actually says

OpenAPI Doc Sync (Daily)

Keeps an OpenAPI-spec-following doc set current with the codebase — the codebase is the source of truth, the spec follows it, not the other way around.

Steps

  1. Find the API surface in code (routers/controllers/handlers — search for route decorators/registrations) and the existing spec file(s) (openapi.yaml/openapi.json or generated docs directory).

  2. Diff reality vs. spec:

    • New endpoints/methods present in code but missing from the spec → add
    • Endpoints in the spec no longer present in code → flag for removal (don't silently delete; an EM/owner should confirm deprecation)
    • Changed request/response shapes (new required fields, changed types, new status codes) → update + log as a "key change"

  3. Update the spec following OpenAPI conventions:

    • Correct paths, parameters, requestBody, responses, components/schemas
    • Keep tags aligned with the existing catalog grouping

  4. Bump info.version (semver: patch for additive/non-breaking, minor for new endpoints, major for breaking changes) and append to a changelog section:

    ## v<version> — <date>
- Added: `POST /v2/widgets` (new endpoint)
- Changed: `GET /users/{id}` now returns `roles[]` (was single `role`)
- Deprecated: `GET /v1/legacy-search` (superseded by `/v2/search`)

  5. Show the diff for review — don't merge spec changes silently, especially anything marked "Changed" or "Deprecated" (those affect consumers).

Notes

  • Schedule via /schedule for a daily run (e.g. after the nightly build/merge).
  • Never invent a field or endpoint — only document what's actually in the code.
  • Breaking changes (removed fields, changed types, new required params) are the most important thing to surface clearly — lead with those.
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. 3d ago First seen · 45 lines · 38 tokens per session scan A 9ef21fc6573f

Subscribe to this mod's changes

openapi-doc-sync is a skill published in the GitHub repository Aibier/claude-em-toolkit (5 stars, last pushed 2mo ago), licensed MIT. It adds 38 tokens to every session and 488 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.

Backend and APIsWriting and docs
Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens