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/popoloni/non_deterministic_sw_eng/securitygit clone --depth 1 https://github.com/popoloni/non_deterministic_sw_engWhat 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.00000 | $0.00628 |
| Opus 5 | $0.00000 | $0.00314 |
| Sonnet 5 | $0.00000 | $0.00126 |
| Haiku 4.5 | $0.00000 | $0.00063 |
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.
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
});
}
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.
- 2d ago First seen · 108 lines · 0 tokens per session scan A 1e1414305ae9
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.
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.
cli-error-handling
CLI command error handling patterns.
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.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.