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/Farzannajipour/cursor-react-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/farzannajipour/cursor-react-rules/security-patterns)<a href="https://agentmods.dev/rules/farzannajipour/cursor-react-rules/security-patterns"><img src="https://agentmods.dev/badge/rules/farzannajipour/cursor-react-rules/security-patterns/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/farzannajipour/cursor-react-rules/security-patterns"><img src="https://agentmods.dev/badge/rules/farzannajipour/cursor-react-rules/security-patterns.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.01249 | $0.01249 |
| Opus 5.5 | $0.00500 | $0.00500 |
| Sonnet 5.5 | $0.00250 | $0.00250 |
| Haiku 4.5 | $0.00125 | $0.00125 |
Grade A, and why
security-patterns 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 — 225 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Patterns
Input Validation
Always validate user input:
import { z } from 'zod';
const schema = z.object({
email: z.string().email(),
password: z.string().min(8),
});
// Validate before using
const result = schema.safeParse(userInput);
if (!result.success) {
throw new Error('Invalid input');
}
XSS Prevention
Escape user-generated content:
// ✅ React escapes by default
<div>{userInput}</div>
// ❌ Dangerous - only use with trusted content
<div dangerouslySetInnerHTML={{ __html: userInput }} />
// ✅ If you must use HTML, sanitize first
import DOMPurify from 'isomorphic-dompurify';
<div dangerouslySetInnerHTML={{ __html: DOMPurify.sanitize(userInput) }} />
Authentication
Server-side auth checks:
// ✅ Check on server
export default async function ProtectedPage() {
const session = await getServerSession();
if (!session) redirect('/login');
return <div>Protected content</div>;
}
// ❌ Don't rely only on client
'use client';
export function Page() {
if (!user) return <LoginPrompt />; // Can be bypassed
}
API Security
Validate and authenticate API routes:
export async function POST(request: Request) {
// 1. Authenticate
const session = await getServerSession();
if (!session) {
return Response.json({ error: 'Unauthorized' }, { status: 401 });
}
// 2. Validate input
const body = await request.json();
const validated = schema.parse(body);
// 3. Authorize (check permissions)
if (!canUserPerformAction(session.user, validated)) {
return Response.json({ error: 'Forbidden' }, { status: 403 });
}
// 4. Process request
const result = await processRequest(validated);
return Response.json(result);
}
Sensitive Data
Never expose secrets:
// ❌ Never
const API_KEY = 'sk_live_12345';
console.log(process.env.SECRET_KEY);
// ✅ Use server-only variables
// Server Component or API Route only
const apiKey = process.env.SECRET_KEY;
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 · 225 lines · 1,249 tokens per session scan A f6e3d2d9c7bf
security-patterns is a cursor rule published in the GitHub repository Farzannajipour/cursor-react-rules (3 stars, last pushed 8mo ago), licensed MIT. It adds 1,249 tokens to every session, about $0.0050 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-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.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
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.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).