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/farzannajipour/cursor-react-rules/security-patternsgit clone --depth 1 https://github.com/Farzannajipour/cursor-react-rulesWhat 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 | $0.01249 | $0.01249 |
| Opus 5 | $0.00624 | $0.00624 |
| Sonnet 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 yesterday.
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.
- yesterday 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 (2 stars, last pushed 7mo ago), licensed MIT. It adds 1,249 tokens to every session, about $0.0062 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.
Other cursor rules, from other repositories
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.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.