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 tomzx/agents --skill review-api-changesgit clone --depth 1 https://github.com/tomzx/agentsWrote 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/tomzx/agents/review-api-changes)<a href="https://agentmods.dev/skills/tomzx/agents/review-api-changes"><img src="https://agentmods.dev/badge/skills/tomzx/agents/review-api-changes/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/tomzx/agents/review-api-changes"><img src="https://agentmods.dev/badge/skills/tomzx/agents/review-api-changes.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.00090 | $0.05002 |
| Opus 5.5 | $0.00036 | $0.02001 |
| Sonnet 5.5 | $0.00018 | $0.01000 |
| Haiku 4.5 | $0.00009 | $0.00500 |
Grade A, and why
review-api-changes 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 6d 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 — 412 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review API Changes
Reviews a change to an API contract and reports findings. It answers one question: will this change break an existing consumer, and if so is that handled? Covering breaking-change detection, additive compatibility, versioning and deprecation, resource and method semantics, status codes and error bodies, pagination, auth and rate limits, idempotency, and schema-to-code drift.
The contract is what a consumer compiles against or calls over the wire.
A field type change, a new required parameter, or a removed enum value is a breaking change even when the handler is correct.
It is the change-time companion to /review-pr, which keeps general code craft, and to /review-sdk-changes, which reviews the client library wrapping the contract.
This review is static: it does not call the API, so behavior observed against a running service is /verify-pr's to prove.
Prerequisites
- Apply the shared SDLC conventions in
skills/sdlc/references/shared.md(PR Review Reports for report location and posting rules). - Apply the shared evidence standard in
../sdlc/references/evidence.md. Static claims carryL1 - CitedorL2 - Ruled out; a decisive claim proven by a read-only command (for example diffing two schema files) can reachL3 - Executed. - The change to review, in one of these forms:
- a PR number plus repository (
/review-api-changes 42 acme/api), - a git diff ref (for example
origin/main..HEAD), - a worktree directory, or a changeset already in context.
- a PR number plus repository (
- The contract at the base revision, so before/after can be compared: the route definitions, the OpenAPI or proto schema, the serializers, and the validation rules.
- The published schema file when the project keeps one, to check schema-to-code drift.
.sdlc/features/N-<slug>/specifications.mdwhen one exists (optional; used for contract-vs-spec checks).
Skill attribution (GitHub)
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.
- 6d ago Changed · -2 lines 2f4cc13ee6e3
- 9d ago Changed · +12 lines 6209be57b7e8
- 11d ago First seen · 402 lines · 90 tokens per session scan A 526dcef5b327
review-api-changes is a skill published in the GitHub repository tomzx/agents (13 stars, last pushed yesterday), licensed MIT. It adds 90 tokens to every session and 5,002 once invoked, about $0.0004 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-10-19.
Other skills, from other repositories
platform-apex-generate
Primary Apex authoring skill for class generation, refactoring, and review. ALWAYS ACTIVATE when the user mentions Apex, .cls, triggers, or asks to create/refactor a class (service, selector, domain, batch, queueable, schedulable, invocable, DTO, utility, interface, abstract, exception, REST resource). Use this skill…
flow-next-impl-review
Carmack-level implementation review of changes via the configured backend. Use when asked to review code or a diff in a flow-next repo.
flow-next-resolve-pr
Resolve PR review feedback. Fetches unresolved threads, triages, fixes, replies and resolves via GraphQL. Use when asked to address review comments.
api-contract-review
Use when auditing CloudBase cloud API wrappers, MCP tools, generated action metadata, or related docs for outdated or incorrect action names, parameters, casing, request shapes, or missing contract tests, especially during periodic quality review or before preparing corrective PRs.
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…
principle-model-the-domain
Apply when writing stateful logic, or when code branches a lot or repeats a shape assumption across files.