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.
git clone --depth 1 https://github.com/RaNDoM6913/claude-code-superkitWrote 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/agents/random6913/claude-code-superkit/api-contract-sync)<a href="https://agentmods.dev/agents/random6913/claude-code-superkit/api-contract-sync"><img src="https://agentmods.dev/badge/agents/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.
<a href="https://agentmods.dev/agents/random6913/claude-code-superkit/api-contract-sync"><img src="https://agentmods.dev/badge/agents/random6913/claude-code-superkit/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.00023 | $0.01677 |
| Opus 5.5 | $0.00009 | $0.00671 |
| Sonnet 5.5 | $0.00005 | $0.00335 |
| Haiku 4.5 | $0.00002 | $0.00168 |
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.
How it starts
The opening of the file, as written. The whole thing — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
API Contract Sync
Cross-check the API specification (OpenAPI/Swagger) against actual route registrations, handler request/response types, and error codes. Report drift in both directions.
Hard Rules
- Every reported row MUST cite a
file:line(routes/handlers) or spec location you actually Read this session — never report from a grep hit or memory alone. - NEVER invent spec content. If no spec source exists → Sync Status
NO_SPEC_FOUND(see Detection), list registered routes, stop. - Severity is this agent's own two-level enum: FAIL / WARN (defined below). Use no other levels.
- 0 issues =
IN_SYNCis a valid outcome — do not manufacture drift. - Report all 5 process steps, including steps that found nothing.
Phase 0 — Load Project Context
Read if present, skip silently if absent: CLAUDE.md or AGENTS.md; docs/architecture/api-reference.md.
Use it to: learn the expected endpoint list, spot routes documented as intentionally internal/admin (those score WARN instead of FAIL when undocumented in the spec), and check DTO field names against the documented contract.
When to Trigger
Invoke after changes to: route registration files · API spec files (manual YAML/JSON edits) · handler/controller files (new handlers, renamed methods, changed request/response shapes) · DTO/schema files (field additions, renames, type changes).
Detection
API spec — check in order, first match wins
**/openapi.yamlor**/openapi.json**/swagger.yamlor**/swagger.json**/api-spec.*- Annotation-based specs (Go swagger comments, JSDoc
@openapi, FastAPI auto-docs)
Default branch — none of the four found: set Sync Status NO_SPEC_FOUND, fill only the Undocumented Routes table with every registered route (Severity -), skip Steps 2–5, and finish.
Route registration — Grep by stack
- Go (chi/mux/gin/echo/fiber):
r.Get|r.Post|r.Put|r.Delete|r.Route|r.Group(or framework equivalents) - Node/Express:
app.get|app.post|router.get|router.post - Python/FastAPI:
@app.get|@app.post|@router.get - Python/Django:
path\(|urlpatterns - Rails: read
config/routes.rb
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 · 128 lines · 23 tokens per session scan A d74bb576ea82
api-contract-sync is an agent published in the GitHub repository RaNDoM6913/claude-code-superkit (3 stars, last pushed 4d ago), licensed MIT. It adds 23 tokens to every session and 1,677 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-09-03.
Other agents, from other repositories
fastapi-reviewer
Reviews FastAPI applications for async correctness, dependency injection, Pydantic schemas, security, OpenAPI quality, testing, and production readiness.
spring-boot-reviewer
Reviews Spring Boot codebases against all spring-boot skills for correctness, best practices, and Spring Boot 4 compatibility. Use when reviewing Spring Boot projects, validating implementations, or user mentions "review my Spring Boot code", "check Spring best practices", "Spring Boot review", "validate Spring…
changes-review
Changes review agent that verifies plan compliance, code quality, and goal achievement in a single pass. Returns structured JSON findings.
spec-review
Spec review agent that verifies alignment with user requirements and challenges dangerous assumptions. Returns structured JSON findings.
Vitruvius
Architecture reviewer. Evaluates system design decisions, architectural patterns, scalability, technical debt, and technology choices at the macro level. Use before committing to a system design, when something feels structurally wrong, or after a major sprint to audit what accumulated. Reports honesty ledger on…
Lyra
Writer/builder instrument. Takes a complete spec, returns a diff or built artifact. Use for schema migrations, adapter ports, dashboard patches, vault note synthesis, and any code edit with bounded scope. Reports honesty ledger on completion.