security

A set of coding rules for authentication, access control, input validation, database queries, cookies, and other sensitive data handling.

In plain words
What is it for?
Use it when building or reviewing code that handles sign-in, permissions, user input, cookies, tokens, or private data.
Why use it?
It helps prevent common security weaknesses such as token leaks, timing attacks, cross-site scripting, SQL injection, and weak login protections.

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/popoloni/non_deterministic_sw_eng/security
Clone the repo
git clone --depth 1 https://github.com/popoloni/non_deterministic_sw_eng
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 628 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.00628
Opus 5 $0.00000 $0.00314
Sonnet 5 $0.00000 $0.00126
Haiku 4.5 $0.00000 $0.00063

Measured 2d ago against content hash 1e1414305ae9, 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 2d 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.

04-context-engineering/cursor-rules/security.mdc · 108 lines

How it starts

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

Security Guidelines

When writing code that handles authentication, authorization, or sensitive data:

Authentication

  • Use constant-time comparison for token validation
  • Never log token contents, only token IDs
  • Set secure cookie flags: httpOnly, secure, sameSite
  • Implement rate limiting (max 5 attempts per minute)
  • Return identical error messages for "user not found" and "wrong password"
// GOOD: Constant-time comparison
import { timingSafeEqual } from 'crypto';

function verifyToken(provided: string, expected: string): boolean {
  const a = Buffer.from(provided);
  const b = Buffer.from(expected);
  if (a.length !== b.length) return false;
  return timingSafeEqual(a, b);
}

// BAD: Vulnerable to timing attacks
function verifyToken(provided: string, expected: string): boolean {
  return provided === expected; // DON'T DO THIS
}

Input Validation

  • Validate ALL user input at API boundary
  • Use allowlists, not blocklists
  • Sanitize output for XSS prevention
  • Use parameterized queries (NEVER string concatenation)
// GOOD: Parameterized query
const user = await prisma.user.findUnique({
  where: { id: userId }
});

// BAD: SQL injection vulnerability
const user = await prisma.$queryRaw`
  SELECT * FROM users WHERE id = ${userId}  // DON'T DO THIS
`;

Secrets Management

  • Store secrets in environment variables
  • Never commit secrets to git
  • Use secret scanning in CI/CD
  • Rotate secrets regularly
// GOOD: Environment variable
const apiKey = process.env.API_KEY;

// BAD: Hardcoded secret
const apiKey = 'sk-1234567890abcdef'; // DON'T DO THIS

Error Handling

  • Never expose stack traces to users
  • Log errors with context, but sanitize sensitive data
  • Return generic error messages to clients
// GOOD: Safe error response
catch (error) {
  logger.error('Authentication failed', { 
    userId: user.id,  // OK to log
    // token: token,  // NEVER log tokens
  });
  return res.status(401).json({ 
    error: 'Authentication failed' 
  });
}

// BAD: Exposes internal details
catch (error) {
  return res.status(500).json({ 
    error: error.message,
    stack: error.stack  // DON'T DO THIS
  });
}

Read the full file on GitHub · 108 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. 2d ago First seen · 108 lines · 0 tokens per session scan A 1e1414305ae9

Subscribe to this mod's changes

security is a cursor rule published in the GitHub repository popoloni/non_deterministic_sw_eng (6 stars, last pushed 8mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 628 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-31.