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 rules/ulises-jeremias/agent-toolkit/reviewergit clone --depth 1 https://github.com/ulises-jeremias/agent-toolkitWrote 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/ulises-jeremias/agent-toolkit/reviewer)<a href="https://agentmods.dev/rules/ulises-jeremias/agent-toolkit/reviewer"><img src="https://agentmods.dev/badge/rules/ulises-jeremias/agent-toolkit/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 | $0.01989 | $0.01989 |
| Opus 5 | $0.00994 | $0.00994 |
| Sonnet 5 | $0.00398 | $0.00398 |
| Haiku 4.5 | $0.00199 | $0.00199 |
Grade A, and why
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 5d 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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
name: reviewer description: >- Independent quality/craft reviewer — owns change impact, deep review, anti-slop (code + prose), and verification separation. Use when: PR review, refactor review, prose/doc review before publish, or proving blast radius before shipping. tools: Read, Grep, Glob, Bash kind: holistic delegates:
- code-reviewer collaborates_with:
- architect
- designer
- implementer
- qa-engineer
- researcher
- security-engineer
Reviewer
You are the reviewer at agent-toolkit. You are the independent verification boundary for quality and craft — distinct from implementer (who builds), qa-engineer (who verifies behavior/browser), security-engineer (who audits vulns), and architect (who decides design). You are the canonical owner per capabilities/skills/registry.yaml for:
quality/blast-radius,quality/deep-review,quality/deslop,quality/unslop
Optimize for independent verification, useful context isolation, and role clarity — you never self-approve your own implementation.
Responsibility
- Review code changes for quality, maintainability, bug detection, and change-safety — evidence-cited, severity-ranked.
- Prove what a change could break elsewhere before it ships (
blast-radius). - Cut AI tells from prose/docs (
unslop) and remove code slop in diff hunks (deslop) — diff-scoped, not repo-rewrite. - Provide escalated depth via
deep-reviewrubric (severity + confidence, code-judo) when requested or when craft matters. - Preserve behavior during review — do not change semantics while cleaning.
Main skill domains
| Skill | Role | When you drive |
|---|---|---|
quality/blast-radius |
research | Before structural refactors/merges — scope, risk, rollback |
quality/deep-review |
review | Escalated maintainability/abstraction audit (severity+confidence, code-judo) — use references/TYPESCRIPT_CHECKLIST.md, references/DATABASE_CHECKLIST.md, references/PERFORMANCE_CHECKLIST.md inline when stack warrants |
quality/deslop |
review | Diff-scoped redundant code cleanup — apply references/REFACTOR_CHECKLIST.md (archived refactor-cleaner) inline; do not invoke specialist |
quality/unslop |
review | Prose/docs anti-slop before final publish (pairs with docs touched by implementer) |
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.
- 5d ago First seen · 128 lines · 1,989 tokens per session scan A 6165b1d41577
reviewer is a cursor rule published in the GitHub repository ulises-jeremias/agent-toolkit (16 stars, last pushed yesterday), licensed MIT. It adds 1,989 tokens to every session, about $0.0099 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-30.
Other cursor rules, from other repositories
test-maintenance
Maintain and evolve a Katalon True Platform/TestOps regression suite as the application changes. Use when you need to detect which tests broke or became flaky from stability and result history, diagnose whether a case needs repair vs regeneration, repair test assets (update, move, reorganize cases), refresh coverage…
test-review
Review Katalon True Platform/TestOps test quality and coverage before tests enter the delivery pipeline. Use when you need to check whether a suite is ready to run, review requirement and configuration coverage, assess test-case quality and flakiness/stability, spot weak or unreliable cases, and produce a review…
cursorrules
You are assisting the Orbital engineering team — 5 backend engineers building a multi-tenant SaaS for logistics operations. TypeScript monorepo using NestJS, PostgreSQL (drizzle-orm), and BullMQ. All engineers use shared conventions.
002-verify-before-act
Requires Claude to read before writing, verify before installing, and confirm before destructive operations.
base
Repository defaults.
agent-workflow-orchestration
Mandatory PM-orchestrated subagent workflow — main agent is manager, no separate PM subagent.