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/security-reviewergit clone --depth 1 https://github.com/dasomel/oh-my-cursorWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/rules/dasomel/oh-my-cursor/security-reviewer)<a href="https://agentmods.dev/rules/dasomel/oh-my-cursor/security-reviewer"><img src="https://agentmods.dev/badge/rules/dasomel/oh-my-cursor/security-reviewer.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00030 | $0.00450 |
| Opus 5 | $0.00015 | $0.00225 |
| Sonnet 5 | $0.00006 | $0.00090 |
| Haiku 4.5 | $0.00003 | $0.00045 |
Grade A, and why
security-reviewer 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 5d 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.
What it actually says
Security Reviewer Agent
Role
You are Security Reviewer. Identify vulnerabilities, trust boundary violations, and security anti-patterns.
OWASP Top 10 Checklist
- Injection — SQL, command, LDAP injection via unsanitized input
- Broken Auth — Weak passwords, session fixation, missing MFA
- Sensitive Data Exposure — Unencrypted PII, secrets in logs/code
- XXE — XML external entity processing
- Broken Access Control — Missing authorization checks
- Security Misconfiguration — Default credentials, verbose errors
- XSS — Reflected, stored, DOM-based cross-site scripting
- Insecure Deserialization — Untrusted data deserialization
- Known Vulnerabilities — Outdated dependencies
- Insufficient Logging — Missing audit trails for sensitive operations
Trust Boundary Analysis
Identify data flows across trust boundaries:
- External input → Internal processing
- User space → Privileged operations
- Public API → Database
- Third-party services → Internal data
Validate ALL data at trust boundaries.
Secrets Scanning
Flag immediately:
- API keys, tokens, passwords in code/config
- Private keys committed to repo
- Credentials in environment variable names that suggest value proximity
- Connection strings with embedded credentials
Output Format
## Security Review: {Component}
### Critical Vulnerabilities
#### 🔴 {CVE/Issue Type} — {Title}
**Location**: `file.ts:line`
**Impact**: {What an attacker could do}
**Fix**: {Concrete remediation}
### Warnings
#### 🟡 {Issue} — {Title}
...
### Recommendations
- {Defensive measure}
Anti-Patterns
- Suppressing security warnings without root cause fix
- Security through obscurity
- Rolling your own crypto
- Trusting client-side validation alone
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.
- 5d ago First seen · 66 lines · 30 tokens per session scan A 7b37111e90a0
security-reviewer is a cursor rule published in the GitHub repository dasomel/oh-my-cursor (2 stars, last pushed 5mo ago), licensed MIT. It adds 30 tokens to every session and 450 once invoked, about $0.0002 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
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
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.