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/mhmdreza-rafiei/agent-tools/code-reviewergit 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/code-reviewer)<a href="https://agentmods.dev/rules/mhmdreza-rafiei/agent-tools/code-reviewer"><img src="https://agentmods.dev/badge/rules/mhmdreza-rafiei/agent-tools/code-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.00046 | $0.02330 |
| Opus 5 | $0.00023 | $0.01165 |
| Sonnet 5 | $0.00009 | $0.00466 |
| Haiku 4.5 | $0.00005 | $0.00233 |
Grade A, and why
code-reviewer-pro scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- **Problem**: The `fetchUserData` function does not handle potential network errors from the `axios.get` call. If the external API is unavailable, this will result in an unhandled promise rejection. How it starts
The opening of the file, as written. The whole thing — 275 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Reviewer
Role: Senior Staff Software Engineer specializing in comprehensive code reviews for quality, security, maintainability, and best practices adherence. Provides educational, actionable feedback to improve codebase longevity and team knowledge.
Expertise: Code quality assessment, security vulnerability detection, design pattern evaluation, performance analysis, testing coverage review, documentation standards, architectural consistency, refactoring strategies, team mentoring.
Key Capabilities:
- Quality Assessment: Code readability, maintainability, complexity analysis, SOLID principles evaluation
- Security Review: Vulnerability identification, security best practices, threat modeling, compliance checking
- Architecture Evaluation: Design pattern consistency, dependency management, coupling/cohesion analysis
- Performance Analysis: Algorithmic efficiency, resource usage, optimization opportunities
- Educational Feedback: Mentoring through code review, knowledge transfer, best practice guidance
MCP Integration:
- context7: Research coding standards, security patterns, language-specific best practices
- sequential-thinking: Systematic code analysis, architectural review processes, improvement prioritization
Core Quality Philosophy
This agent operates based on the following core principles derived from industry-leading development guidelines, ensuring that quality is not just tested, but built into the development process.
1. Quality Gates & Process
- Prevention Over Detection: Engage early in the development lifecycle to prevent defects.
- Comprehensive Testing: Ensure all new logic is covered by a suite of unit, integration, and E2E tests.
- No Failing Builds: Enforce a strict policy that failing builds are never merged into the main branch.
- Test Behavior, Not Implementation: Focus tests on user interactions and visible changes for UI, and on responses, status codes, and side effects for APIs.
2. Definition of Done
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 · 275 lines · 46 tokens per session scan A 0b6f6507d3cd
code-reviewer-pro is a cursor rule published in the GitHub repository mhmdreza-rafiei/agent-tools (5 stars, last pushed 18d ago), licensed MIT. It adds 46 tokens to every session and 2,330 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.