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.
git clone --depth 1 https://github.com/squirrelogic/cursor-rulesWrote 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/squirrelogic/cursor-rules/code-review)<a href="https://agentmods.dev/rules/squirrelogic/cursor-rules/code-review"><img src="https://agentmods.dev/badge/rules/squirrelogic/cursor-rules/code-review/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/squirrelogic/cursor-rules/code-review"><img src="https://agentmods.dev/badge/rules/squirrelogic/cursor-rules/code-review.svg" alt="Reviewed on agentmods" width="80" 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.01630 | $0.01630 |
| Opus 5.5 | $0.00652 | $0.00652 |
| Sonnet 5.5 | $0.00326 | $0.00326 |
| Haiku 4.5 | $0.00163 | $0.00163 |
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 1mo 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 — 289 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Review Guidelines
Review Process
-
Before Starting Review:
- Check task requirements and acceptance criteria
- Review related tasks and dependencies
- Understand the context of the changes
-
During Review:
- Follow checklist systematically
- Document findings clearly
- Provide constructive feedback
- Reference specific rules when applicable
-
After Review:
- Verify fixes address all comments
- Check if changes require task updates
- Update documentation if needed
Review Checklist
Architecture & Structure
// ✅ DO: Proper server action structure
// app/actions/organization/create.ts
'use server'
import { createOrganization } from '@/lib/data/mutations/organizations'
// ❌ DON'T: Mix concerns
'use server'
import { db } from '@/db'
// Direct database operations in server action
- Next.js 15 app directory structure
- Server actions in
app/actions/ - Database operations in
lib/data/{queries,mutations}/ - shadcn/ui component patterns
- SOLID principles adherence
- Clean data access patterns
Database & Data Layer
// ✅ DO: Use Drizzle migrations
// db/migrations/0001_initial.ts
import { sql } from 'drizzle-orm'
// ❌ DON'T: Manual SQL files
// migrations/manual.sql
CREATE TABLE users...
- Generated Drizzle migrations
- Proper RLS policies
- Edge function security
- PostgreSQL style compliance
- Type-safe database operations
- Query optimization
Server Actions & API
// ✅ DO: Proper server action
export async function createUser(input: CreateUserInput) {
const result = await createUserMutation(input);
if (result.error) {
return { error: result.error };
}
return { data: result.data };
}
// ❌ DON'T: Skip validation/typing
export async function createUser(formData: any) {
const user = await db.users.create(formData);
return user;
}
- 'use server' directive present
- Abstracted database operations
- Comprehensive error handling
- Zod schema validation
- Proper async patterns
- Appropriate response handling
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.
- 1mo ago First seen · 289 lines · 1,630 tokens per session scan A 66d9b2e4ec04
code-review is a cursor rule published in the GitHub repository squirrelogic/cursor-rules (20 stars, last pushed 1y ago), licensed MIT. It adds 1,630 tokens to every session, about $0.0065 per session on Opus 5.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
clean-code-reviewer
Eliminates technical debt using SOLID, DRY, YAGNI, and Addy Osmani production-grade engineering principles. / TR: SOLID, DRY, YAGNI ve Addy Osmani üretim seviyesi mühendislik ilkeleri ile kod kalitesini denetleyen yetenek.
sweep-benchmarks
Audit xrspatial modules for asv benchmark coverage gaps: missing benchmarks, backend parameterization gaps, unrepresentative inputs, broken or silently-skipped benchmarks.
code-review
BMAD BMM Agent: code-review.
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.