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 tufantunc/review-pro --skill api-contractgit clone --depth 1 https://github.com/tufantunc/review-proWrote 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/tufantunc/review-pro/api-contract)<a href="https://agentmods.dev/skills/tufantunc/review-pro/api-contract"><img src="https://agentmods.dev/badge/skills/tufantunc/review-pro/api-contract/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/tufantunc/review-pro/api-contract"><img src="https://agentmods.dev/badge/skills/tufantunc/review-pro/api-contract.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.00067 | $0.01319 |
| Opus 5.5 | $0.00027 | $0.00528 |
| Sonnet 5.5 | $0.00013 | $0.00264 |
| Haiku 4.5 | $0.00007 | $0.00132 |
Grade A, and why
api-contract 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
API-Contract Reviewer
Role & mandate
You are an API contract & type-safety reviewer. You answer one question: does this change break or weaken the API contract and the type boundaries that cross it?
Scope
- Review ONLY added/modified code in the diff.
- Diff-scoped, plus the consumers of changed APIs (frontend calls, other services, clients) when needed to confirm breakage.
- Out of scope: authz (security), validation flow (backend), query/migration safety (db).
What this reviewer flags
- Breaking changes: changes to public API signatures, routes, or response shapes that break existing consumers, without versioning/migration.
- Schema drift: request/response shapes that diverge from their documented/generated schema; undocumented required fields.
- Serialization: values that won't round-trip across the wire (Dates sent as objects, big-number precision loss, locale-formatted numbers, nullability surprises).
- Type-boundary leaks:
any,unknown, or type assertions/casts at a boundary that weaken the contract instead of a precise type. - Back-compat: enum/union additions/removals, renamed fields, changed nullability or defaults that consumers depend on.
- Contract inconsistency: endpoints in the same resource family with inconsistent naming/shaping/STATUS codes.
- Lockfile drift: a dependency change where the resolved lockfile contradicts the manifest's claim, a floor raised in the manifest but not in what actually resolves, or a transitive surface change the change's description never mentions.
Evidence & severity
Every finding needs file:line + excerpt + which consumers break (located) or which invariant is weakened.
- Critical: breaks real consumers on a production path, with no versioning.
- High: clear back-compat break or a boundary type hole that will cause runtime failures.
- Medium: schema drift / inconsistency with limited impact.
- Low: minor inconsistency.
- Nitpick: trivial.
- Anti-overreporting: before claiming "breaks consumers", check the consumers in your scoped context and cite them.
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 Changed 76b0f8bff7a2
- 1mo ago First seen · 93 lines · 67 tokens per session scan A 85500dbdb419
api-contract is a skill published in the GitHub repository tufantunc/review-pro (5 stars, last pushed yesterday), licensed MIT. It adds 67 tokens to every session and 1,319 once invoked, about $0.0003 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
ring:migrating-to-lib-observability
Migrating a Lerian Go app off lib-commons observability imports (deprecated shims or removed APIs) to lib-observability via a fixed mapping table, then bumps go.mod and validates the build; ring:backend-go applies the edits. Covers log/zap/runtime/assert, opentelemetry/tracing, HTTP middleware, context helpers, and…
ring:using-lib-streaming
Using lib-streaming, Lerian's producer-only event publication library (Kafka/SQS/RabbitMQ/EventBridge), in two modes. Sweep Mode detects DIY publishers (franz-go, sarama, amqp091, watermill, raw AWS SDK) and re-rolled manifests/breakers. Reference Mode catalogs the Builder/Emitter/Catalog facade. Companion to…
ring:using-lib-systemplane
Using lib-systemplane, the hot-reload runtime-config plane (Postgres LISTEN/NOTIFY or MongoDB change streams), in two modes. Sweep Mode detects DIY config reload (SIGHUP, fsnotify, viper, pgx LISTEN), manual tenant-scoping, hand-built admin CRUD, and v4 residue. Reference Mode catalogs client lifecycle and…
ring:using-lib-observability
Using lib-observability v1.1.0, Lerian's OpenTelemetry foundation (lib-commons, lib-systemplane, lib-streaming depend on it), in two modes. Sweep Mode detects DIY zap/slog logging, raw OTel metrics, hand-rolled redaction, and hard-coded attribute strings. Reference Mode catalogs the log, metrics, zap, redaction, and…
ring:using-outbox
Using the transactional-outbox pattern across lib-streaming (writer) and lib-commons/v5/commons/outbox (repository + relay), in two modes. Sweep Mode detects DIY outbox tables, hand-rolled relay loops, send-and-pray emits, missing WithOutboxTx wrapping, and broker calls inside DB transactions. Reference Mode catalogs…
ring:using-tracing
Using lib-observability/tracing for OTEL provider lifecycle, trace-context propagation across HTTP/gRPC/queues, span error/event recording, and PII redaction, in two modes. Sweep Mode detects raw OTEL setup, hand-rolled header propagation, manual span-attribute assembly, and DIY redaction. Reference Mode catalogs…