agentmods.dev

code-review

A structured review of a proposed code change before it is approved or merged. A pull request is a request to add changes to a shared codebase.

In plain words
What is it for?
Use it to review pull requests, check security-sensitive code and test coverage, and separate important issues from optional style suggestions.
Why use it?
It helps catch correctness problems, security risks, missing tests, and regressions before the change ships.

Command for Cursor

9 25d ago A scan 10 tokens original MIT
View the source file emaraschio/cursor-commands
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 commands/emaraschio/cursor-commands/code-review
Clone the repo
git clone --depth 1 https://github.com/emaraschio/cursor-commands

Made for: Cursor.

Per session 10 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 381 The whole file, excluding the scripts and references it only reads on demand.
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.00010 $0.00381
Opus 5 $0.00005 $0.00191
Sonnet 5 $0.00002 $0.00076
Haiku 4.5 $0.00001 $0.00038

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

Security

Grade A, and why

code-review 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.

.cursor/commands/code-review.md · 38 lines

What it actually says

Overview

Thorough PR code review before approval. Full workflow: .cursor/skill-contracts/code-review/SKILL.md (user install: ~/.cursor/skill-contracts/code-review/SKILL.md).

Defaults

None. See skill for workflow defaults.

Steps

  1. Read .cursor/skill-contracts/code-review/SKILL.md for the full agent contract; if that file is missing, read ~/.cursor/skill-contracts/code-review/SKILL.md.
  2. Execute the workflow in order; do not skip safety steps.
  3. Report outcomes per skill (summary, tables, or checklist as specified).

Anti-patterns

  • Check security and tests before approving. Trigger: a change that looks clean on the surface. Wrong: approving without reviewing security-sensitive paths or test coverage. Correct: verify security risks and test coverage before signing off. Reason: an approval is a quality gate, so unverified code ships vulnerabilities and regressions.
  • Weigh substance over style. Trigger: noticing formatting or naming preferences. Wrong: blocking the review on subjective style nits. Correct: focus on correctness, design, and risk, and raise style points as non-blocking. Reason: style nitpicks crowd out substantive feedback and stall the author.

Examples

  • /code-review

Maintainers

Behavioral eval: .cursor/skill-contracts/code-review/eval/cases.md. Ship gate sections: A, S before changing SKILL.md or this command.

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 · 38 lines · 10 tokens per session scan A 5fa3d5169954

Subscribe to this mod's changes

code-review is a command published in the GitHub repository emaraschio/cursor-commands (9 stars, last pushed 25d ago), licensed MIT. It adds 10 tokens to every session and 381 once invoked, about $0.0001 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.

Code reviewSecurityTestingagent-skillsai-agentscursorcursor-idedeveloper-toolsdotfiles
Related

Other commands, from other repositories

grok_init

Discover, verify, and persist the local HTTP proxy used by Grok Build Supervisor.

Vanyangyang/cursor-bridge · 17 tokens

burndown-full

Drive a partially-executed plan to 100% coverage across the whole repo — enumerate, batch-execute, prove completeness.

kensaurus/cursor-kenji · 25 tokens

mcp-guide

Reference for the MCP toolset (Context7, Firecrawl, Playwright, Supabase, Sequential Thinking) and when to reach for each.

kensaurus/cursor-kenji · 28 tokens

ship-and-observe

Take merged, green code to a verified, monitored production release — deploy, confirm the revision is live, smoke-test, observe, and roll back if needed.

kensaurus/cursor-kenji · 31 tokens

debug-issue

Hypothesis-driven debugging with runtime evidence — Sentry, Firecrawl, and Sequential Thinking, not guessing.

kensaurus/cursor-kenji · 20 tokens

grill-me

Relentless one-question-at-a-time interview to sharpen a plan or design before any code is written.

kensaurus/cursor-kenji · 20 tokens