project

A set of Cursor rules that adds slash commands for reviewing code changes. Cursor is a code editor with an AI assistant, and these commands connect reviews to an external code-review service.

In plain words
What is it for?
Use it to review staged changes, all uncommitted changes, branch differences, and potential security problems from within Cursor.
Why use it?
It gives you repeatable commands for checking staged, uncommitted, branch, or security-related changes instead of setting up each review request by hand.

Cursor rule

Install

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.

agentmods
npx agentmods add rules/praneybehl/code-review-mcp/project
Clone the repo
git clone --depth 1 https://github.com/praneybehl/code-review-mcp
Per session 400 This file is loaded in full into every session.
When invoked 400 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00400 $0.00400
Opus 5 $0.00200 $0.00200
Sonnet 5 $0.00080 $0.00080
Haiku 4.5 $0.00040 $0.00040

Measured 2d ago against content hash 9a6f8bf132e0, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

project 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 2d 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.

examples/cursor-rules/project.mdc · 23 lines

How it starts

The opening of the file, as written. The whole thing — 23 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Cursor Code Review Rules

Use these rules to add code review capabilities to Cursor via slash commands.

Slash Commands

/review-staged: Use the perform_code_review tool from the code-reviewer MCP server to review staged changes. Use anthropic provider with claude-3-7-sonnet-20250219 model. Base the task description on our current conversation context and focus on code quality and best practices.

/review-head: Use the perform_code_review tool from the code-reviewer MCP server to review all uncommitted changes (HEAD). Use openai provider with o3 model. Base the task description on our current conversation context and focus on code quality and best practices.

/review-security: Use the perform_code_review tool from the code-reviewer MCP server to review staged changes. Use anthropic provider with claude-3-5-sonnet-20241022 model. Base the task description on our current conversation context and specifically focus on security vulnerabilities, input validation, and secure coding practices.

/review-branch : Use the perform_code_review tool from the code-reviewer MCP server to review changes between the specified branch and HEAD. Use google provider with gemini-2.5-pro-preview-05-06 model. Set diffBase to . Base the task description on our current conversation context and focus on code quality and best practices.

/review-performance: Use the perform_code_review tool from the code-reviewer MCP server to review staged changes. Use openai provider with o3 model. Base the task description on our current conversation context and specifically focus on performance optimizations, computational efficiency, and algorithm improvements.

Notes

  1. Model names: Replace with the latest available models from each provider as they become available.
  2. Task description: Cursor will extract context from your current conversation, but for best results, discuss what you're working on before running a review command.
  3. Branch parameter: While the MCP server sanitizes inputs, avoid using branch names with special characters.

Read the full file on GitHub · 23 lines

Changes

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.

  1. 2d ago First seen · 23 lines · 400 tokens per session scan A 9a6f8bf132e0

Subscribe to this mod's changes

project is a cursor rule published in the GitHub repository praneybehl/code-review-mcp (33 stars, last pushed 1y ago), licensed MIT. It adds 400 tokens to every session, about $0.0020 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.