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 agentmods add skills/tufantunc/review-pro/api-contractnpx 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.svg" alt="Measured on agentmods" 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 | $0.00067 | $0.01319 |
| Opus 5 | $0.00034 | $0.00660 |
| Sonnet 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 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.
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.
- today Changed 76b0f8bff7a2
- 5d 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 (4 stars, last pushed 4d ago), licensed MIT. It adds 67 tokens to every session and 1,319 once invoked, about $0.0003 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.
Other skills, from other repositories
juror-review
Inspect Juror Cloud PR findings and, only after an explicit confirmation, start or rerun a hosted Juror review.
logic-review
Find logic bugs in a single file or function via semi-formal execution tracing (Premises → Trace → Divergence → Trigger → Remedy). Trigger when a user shares code and suspects something is wrong without naming a concrete failure — phrases like "review this", "does this look right", "check this function", "audit this…
logic-fix-all
Autonomous repository-wide audit-and-fix pipeline: health → review → locate/explain → fix → diff-verify → iterate until clean. Starts with a mandatory consent prompt (token-intensive); after consent runs hands-free. Trigger when the user wants ALL logic issues found and fixed — "fix everything", "fix all logic…
logic-health
Sweep a directory, module, or full codebase for logic correctness and produce a scored health dashboard with systemic patterns. Trigger when the user requests a health view — "audit the whole codebase", "health check", "health overview", "logic health overview", "audit src/", "audit auth and payments modules", "where…
run-iteration-eval
Run the Logic-Lens content-eval pipeline for one iteration and produce a scored summary.json — use to measure a skill change. Wraps scripts/run-content-evals.sh (runner, costs tokens) and scripts/grade-iteration.py (grader, free, re-runnable). ALWAYS sync the plugin cache first. Use when the user wants to "run the…
new-skill
Scaffold a new logic- skill in the Logic-Lens repo and wire it into every place a skill must be registered, so no step is missed. Use when adding a seventh (or later) skill to Logic-Lens.