security-reviewer

security-reviewer is a cursor rule for coding agents from dasomel/oh-my-cursor. It costs 30 tokens per session (450 once invoked), scanned A, original, MIT.

A code-review guide for finding common security weaknesses, unsafe data flows, and exposed secrets. It covers areas such as login checks, permissions, input handling, and sensitive code paths.

In plain words
What is it for?
Use it for security audits, threat modeling, and reviews of authentication, authorization, APIs, databases, and other sensitive code.
Why use it?
It helps spot security problems before they become incidents, especially where data crosses from users or outside services into trusted systems.

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/dasomel/oh-my-cursor/security-reviewer
Clone the repo
git clone --depth 1 https://github.com/dasomel/oh-my-cursor

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

agentmods badge for security-reviewer

README.md
[![agentmods](https://agentmods.dev/badge/rules/dasomel/oh-my-cursor/security-reviewer.svg)](https://agentmods.dev/rules/dasomel/oh-my-cursor/security-reviewer)
Your own site
<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>
Per session 30 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 450 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.1 $0.00030 $0.00450
Opus 5 $0.00015 $0.00225
Sonnet 5 $0.00006 $0.00090
Haiku 4.5 $0.00003 $0.00045

Measured 5d ago against content hash 7b37111e90a0, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, from the pricing page.

Security

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.

rules/agents/security-reviewer.mdc · 66 lines

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
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. 5d ago First seen · 66 lines · 30 tokens per session scan A 7b37111e90a0

Subscribe to this mod's changes

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.