security

A set of security guidelines for authentication, protecting data, validating input, and securing APIs. It includes practices such as hashing passwords with bcrypt or Argon2 and verifying JSON Web Tokens, which are signed credentials used for API access.

In plain words
What is it for?
Use it when designing or reviewing login systems, authorization checks, password handling, tokens, input validation, data protection, and API security.
Why use it?
It helps prevent common security mistakes such as storing plain-text passwords, accepting invalid input, mishandling permissions, or trusting unverified tokens.

Cursor rule

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/renvia-code/best-cursor-rules/security
Clone the repo
git clone --depth 1 https://github.com/Renvia-code/best-cursor-rules
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 1,913 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.00000 $0.01913
Opus 5 $0.00000 $0.00957
Sonnet 5 $0.00000 $0.00383
Haiku 4.5 $0.00000 $0.00191

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

Security

Grade A, and why

security 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.

rules/best-practices/security.mdc · 365 lines

How it starts

The opening of the file, as written. The whole thing — 365 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Security Best Practices

Overview

Area Priority
Authentication Critical
Authorization Critical
Input Validation Critical
Data Protection High
API Security High

Authentication

Password Handling

// ✅ Use bcrypt or argon2 for password hashing
import bcrypt from 'bcrypt'

const SALT_ROUNDS = 12

async function hashPassword(password: string): Promise<string> {
  return bcrypt.hash(password, SALT_ROUNDS)
}

async function verifyPassword(password: string, hash: string): Promise<boolean> {
  return bcrypt.compare(password, hash)
}

// ❌ Never store plain text passwords
// ❌ Never use MD5 or SHA1 for passwords
// ❌ Never log passwords

JWT Tokens

import jwt from 'jsonwebtoken'

// ✅ Short-lived access tokens
const ACCESS_TOKEN_EXPIRY = '15m'

// ✅ Longer refresh tokens (stored securely)
const REFRESH_TOKEN_EXPIRY = '7d'

function generateAccessToken(userId: string): string {
  return jwt.sign(
    { sub: userId, type: 'access' },
    process.env.JWT_SECRET!,
    { expiresIn: ACCESS_TOKEN_EXPIRY }
  )
}

// ✅ Always verify tokens
function verifyToken(token: string): JwtPayload {
  return jwt.verify(token, process.env.JWT_SECRET!) as JwtPayload
}

Session Security

// ✅ Secure cookie settings
const sessionConfig = {
  httpOnly: true,    // Prevents XSS access to cookie
  secure: true,      // HTTPS only (in production)
  sameSite: 'strict', // Prevents CSRF
  maxAge: 24 * 60 * 60 * 1000, // 24 hours
}

Input Validation

Validate All Input

import { z } from 'zod'

// ✅ Define strict schemas
const userSchema = z.object({
  email: z.string().email().max(255),
  password: z.string().min(8).max(100),
  name: z.string().min(1).max(100).regex(/^[a-zA-Z\s]+$/),
})

// ✅ Validate before processing
function createUser(input: unknown) {
  const validated = userSchema.parse(input)
  // Safe to use validated data
}

Prevent SQL Injection

Read the full file on GitHub · 365 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 · 365 lines · 0 tokens per session scan A bd3f801ca402

Subscribe to this mod's changes

security is a cursor rule published in the GitHub repository Renvia-code/best-cursor-rules (12 stars, last pushed 9mo ago), licensed CC0-1.0. It costs nothing until one of its globs matches a file; then it loads 1,913 tokens. 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.