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/dasomel/oh-my-cursor/securitygit clone --depth 1 https://github.com/dasomel/oh-my-cursorWhat 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.00331 | $0.00331 |
| Opus 5 | $0.00166 | $0.00166 |
| Sonnet 5 | $0.00066 | $0.00066 |
| Haiku 4.5 | $0.00033 | $0.00033 |
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.
What it actually says
Security Standards (Always Applied)
Non-Negotiable Rules
Secrets
- NEVER hardcode API keys, passwords, tokens, or credentials
- NEVER commit
.envfiles with real values - Use environment variables or secret managers
- Rotate any secret accidentally committed
Input Validation
- Validate ALL external input at system boundaries
- Use allowlists over denylists
- Validate type, format, length, range
- Reject and log invalid input — never silently ignore
SQL/Command Injection
- Use parameterized queries / prepared statements
- Never concatenate user input into SQL strings
- Never pass user input to shell commands (
exec,spawn)
Authentication & Authorization
- Check authorization on EVERY sensitive operation (don't rely on UI hiding)
- Use established auth libraries — don't roll your own
- Session tokens: httpOnly, secure, sameSite cookies
- Implement rate limiting on auth endpoints
Data Handling
- Encrypt PII at rest and in transit
- Minimize data collection (only what's needed)
- Log context, not sensitive data (log userId, not password)
Dependencies
- Run
npm audit/pip audit/cargo auditregularly - Fix CRITICAL vulnerabilities immediately
- Prefer well-maintained packages (recent commits, many maintainers)
When You See a Violation
Flag immediately with: 🔴 SECURITY: {description} at {file}:{line}
Do not proceed without addressing it.
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 · 46 lines · 331 tokens per session scan A 0c67c0c2360e
security is a cursor rule published in the GitHub repository dasomel/oh-my-cursor (2 stars, last pushed 5mo ago), licensed MIT. It adds 331 tokens to every session, about $0.0017 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.