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 skills add Bidiche49/claude-conf --skill api-contract-syncgit clone --depth 1 https://github.com/Bidiche49/claude-confWrote 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/bidiche49/claude-conf/api-contract-sync)<a href="https://agentmods.dev/skills/bidiche49/claude-conf/api-contract-sync"><img src="https://agentmods.dev/badge/skills/bidiche49/claude-conf/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.
<a href="https://agentmods.dev/skills/bidiche49/claude-conf/api-contract-sync"><img src="https://agentmods.dev/badge/skills/bidiche49/claude-conf/api-contract-sync.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00017 | $0.00372 |
| Opus 5.5 | $0.00007 | $0.00149 |
| Sonnet 5.5 | $0.00003 | $0.00074 |
| Haiku 4.5 | $0.00002 | $0.00037 |
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 1mo 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.
What it actually says
Compare API_CONTRACT.md against the real codebase and report differences. Do NOT modify the contract automatically.
1. Locate the contract
Search in order: shared/API_CONTRACT.md, API_CONTRACT.md, ../shared/API_CONTRACT.md. If not found, tell the user to run /api-contract-init first.
2. Parse the contract
Extract all documented endpoints: method, path, request/response types.
3. Scan the code
Use the same stack detection and route scanning logic as /api-contract-init to find all endpoints currently in the codebase.
4. Compare and classify
| Status | Meaning |
|---|---|
| MISSING | Endpoint exists in code but not in contract |
| REMOVED | Endpoint exists in contract but not in code |
| CHANGED | Endpoint exists in both but signatures differ (params, types, method) |
5. Display the report
API CONTRACT SYNC
=================
[N] endpoints in sync
[If issues found:]
MISSING (in code, not in contract):
[METHOD] [path] — [Controller.method()]
REMOVED (in contract, not in code):
[METHOD] [path] — was in [Controller] (file deleted?)
CHANGED (signatures differ):
[METHOD] [path] — contract says [X], code expects [Y]
If everything is in sync: Contract in sync — [N] endpoints verified.
6. Propose corrections
List suggested updates to the contract but do NOT apply them. Let the user decide.
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.
- 1mo ago First seen · 51 lines · 17 tokens per session scan A 0c1d1cc02e1e
api-contract-sync is a skill published in the GitHub repository Bidiche49/claude-conf (2 stars, last pushed 5mo ago), licensed MIT. It adds 17 tokens to every session and 372 once invoked, about $0.0001 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.
Other skills, from other repositories
llm-provider
Adds a new LLM provider implementing LLMProvider interface with call() and stream() methods. Integrates with provider factory in src/llm/index.ts, config detection in src/llm/config.ts, and error handling via tracking and recovery. Use when adding a new model backend, integrating a third-party LLM API, or extending…
tech-design
A guided process for writing a backend technical design from a product requirements document or feature description. A technical design explains how a feature should work in code and services.
config-manager
Skill that manages configuration.
code-review-helper
A safe skill that helps with code review tasks.
system-admin-helper
Skill with dangerous system commands.
api-interface-design
Use when designing public APIs, module boundaries, provider adapters, tool schemas, or data contracts.