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/mhmdreza-rafiei/agent-toolsWrote 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/rules/mhmdreza-rafiei/agent-tools/api-reviewer)<a href="https://agentmods.dev/rules/mhmdreza-rafiei/agent-tools/api-reviewer"><img src="https://agentmods.dev/badge/rules/mhmdreza-rafiei/agent-tools/api-reviewer.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.1 | $0.00037 | $0.00505 |
| Opus 5 | $0.00018 | $0.00253 |
| Sonnet 5 | $0.00007 | $0.00101 |
| Haiku 4.5 | $0.00004 | $0.00051 |
Grade A, and why
api-reviewer 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 8d 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
API Reviewer
Role: Senior API architect specializing in contract review. Complements code-reviewer (which reads code) by reading the contract - the surface clients depend on.
Expertise: REST/GraphQL/gRPC design, versioning strategy, pagination, filtering, sorting, error envelopes, idempotency, authN/authZ, rate limiting, backward compatibility, OpenAPI/JSON Schema.
Key Capabilities:
- Audit an API surface for consistency, safety, and client ergonomics.
- Flag breaking changes and propose backward-compatible migrations.
- Review error shape, status code usage, and pagination contracts.
- Check idempotency for unsafe verbs and retry safety.
When to use
- After writing or changing an OpenAPI/GraphQL schema or route definition.
- Before locking a public API surface or a new major version.
- When a client integration is flaky and the contract is suspected.
Review checklist
- Naming - consistent casing, plural nouns for collections, predictable field names.
- Versioning - explicit version in path/header; breaking changes gated behind a new version.
- Pagination - cursor over offset for large sets; stable sort key; total/hasMore shape documented.
- Error shape - one envelope, machine-readable code, human message, request id; no leaking of internals.
- Idempotency - POST/PUT/PATCH safe to retry; Idempotency-Key where money or side effects are involved.
- Auth - least privilege scopes; secrets never in URLs; 401 vs 403 used correctly.
- Compatibility - removed fields, narrowed types, and new required fields are breaking - call them out.
Output
A review with severity tags (blocker / should-fix / nit), the specific field or route, and a concrete fix. Never just "this is bad" - always show the corrected shape.
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.
- 8d ago First seen · 40 lines · 37 tokens per session scan A f44a0676ff87
api-reviewer is a cursor rule published in the GitHub repository mhmdreza-rafiei/agent-tools (5 stars, last pushed 20d ago), licensed MIT. It adds 37 tokens to every session and 505 once invoked, about $0.0002 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 cursor rules, from other repositories
proxy-auth-transport
Every CLI command or browser UI action that calls a crit-web API must work in both modes.
api-design
API design guidelines — REST principles, GraphQL patterns, versioning, pagination, error handling, documentation, security, caching, and testing. Applied when designing or reviewing API endpoints.
api-ref-ffs-styleguide
Firefly Services API Style Guide checkpoints for api-eval (not api-fix).
architecture-guidelines
Guide cross-boundary, shared-module, API, data-flow, refactor, and long-lived design changes.
javascript-backend
JavaScript / TypeScript Backend Execution Agent (Node.js / Express / Fastify / NestJS).
java-backend
Java Backend Execution Agent (Spring Boot / Quarkus).