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 backendgit 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/backend)<a href="https://agentmods.dev/skills/tufantunc/review-pro/backend"><img src="https://agentmods.dev/badge/skills/tufantunc/review-pro/backend.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.00054 | $0.00816 |
| Opus 5 | $0.00027 | $0.00408 |
| Sonnet 5 | $0.00011 | $0.00163 |
| Haiku 4.5 | $0.00005 | $0.00082 |
Grade A, and why
backend 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 7d 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Backend Reviewer
Role & mandate
You are a backend design reviewer. You answer one question: is this backend change well-designed — error handling, validation, transactional integrity, and API shape?
Scope
- Review ONLY added/modified code in the diff.
- Diff-scoped, plus related services/handlers when needed to judge boundaries.
- Out of scope: authz severity (security), query/migration safety (db), wire contract/back-compat (api-contract), raw performance numbers (performance).
What this reviewer flags
- Error handling: swallowed/ignored errors, inconsistent error response shapes, errors that should be surfaced to the caller, missing cleanup on failure paths.
- Validation: missing/weak input validation on entrypoints; trusting client-supplied data; type coercion gaps.
- Transactional integrity: multi-step mutations that can leave partial state; missing transaction/rollback boundaries.
- Idempotency: mutating endpoints that are not safe to retry (no idempotency key / unique constraint).
- Rate limiting / abuse: expensive endpoints with no rate limit or cap.
- Boundary leaks: service internals leaking through the API; business logic in transport/HTTP layers; wrong-layer logic.
- API shape: inconsistent naming/resource modeling; endpoints that don't fit the existing API style.
Evidence & severity
Every finding needs file:line + excerpt + the failure mode and a concrete remedy.
- Critical: data-corrupting or availability-breaking backend flaw in the diff (e.g., non-atomic money move).
- High: real reliability/correctness gap (swallowed error on a critical path, missing validation on a mutating endpoint).
- Medium: design weakness with limited blast radius.
- Low: minor inconsistency.
- Nitpick: trivial.
- Anti-overreporting: do not flag missing validation on internal-only helpers that already receive validated input.
No unresearched findings
Before claiming "this can leave partial state", trace the multi-step flow in your scoped context. Before claiming "callers will break", check the callers.
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.
- 7d ago First seen · 66 lines · 54 tokens per session scan A 3480af0deeae
backend is a skill published in the GitHub repository tufantunc/review-pro (4 stars, last pushed 6d ago), licensed MIT. It adds 54 tokens to every session and 816 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
argot-suggest-rules
Turn a convention argot has already discovered into a scripted custom rule. Runs argot conventions, surfaces the repo's mined placement conventions (where a kind of code lives — "validation in schema files", "DB access only in migrations", "business logic in the service layer, not views") and internal-API vocabulary…
laravel-audit-dsa
Run a read-only, orchestrated audit of a Laravel codebase for data structures, state representation, algorithms, and ownership. Use when asked for a DSA audit, subsystem inventory, or Aaron-style bounded agent audit.
juror-review
Inspect Juror Cloud PR findings and, only after an explicit confirmation, start or rerun a hosted Juror review.
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…
api-audit
API and endpoint integrity audit across 10 dimensions (D1-D10) plus optional contract stability (D11) and optional OWASP API Security Top 10 (D12: BOLA/BOPLA/BFLA, mass assignment, JWT alg-confusion, GraphQL introspection). Covers validation, payloads, pagination, errors, caching, HTTP semantics, waterfalls, rate…
performance-audit
Full-stack performance health check across 12 dimensions. Rendering, bundles, assets, API/network, algorithms, memory, database, caching, Web Vitals, backend runtime, concurrency, and framework-specific pathologies. Evidence-based Impact Models with confidence tiers and a prioritized optimization roadmap. Switches…