security-patterns

Rules for protecting software by validating input, preventing cross-site scripting, checking authentication, and securing API routes.

In plain words
What is it for?
Use them when handling user input, rendering user-provided content, protecting pages, or building API endpoints.
Why use it?
They reduce risks such as accepting invalid data, displaying unsafe content, or trusting checks that users can bypass.

Cursor rule for Cursor

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/farzannajipour/cursor-react-rules/security-patterns
Clone the repo
git clone --depth 1 https://github.com/Farzannajipour/cursor-react-rules

Made for: Cursor.

Per session 1,249 This file is loaded in full into every session.
When invoked 1,249 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.01249 $0.01249
Opus 5 $0.00624 $0.00624
Sonnet 5 $0.00250 $0.00250
Haiku 4.5 $0.00125 $0.00125

Measured yesterday against content hash f6e3d2d9c7bf, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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.

.cursor/rules/security-patterns.mdc · 225 lines

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;

Read the full file on GitHub · 225 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. yesterday First seen · 225 lines · 1,249 tokens per session scan A f6e3d2d9c7bf

Subscribe to this mod's changes

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.