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 agents/jy315189/everything-cursor/security-reviewergit clone --depth 1 https://github.com/jy315189/everything-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/agents/jy315189/everything-cursor/security-reviewer)<a href="https://agentmods.dev/agents/jy315189/everything-cursor/security-reviewer"><img src="https://agentmods.dev/badge/agents/jy315189/everything-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 | $0.00000 | $0.00665 |
| Opus 5 | $0.00000 | $0.00332 |
| Sonnet 5 | $0.00000 | $0.00133 |
| Haiku 4.5 | $0.00000 | $0.00067 |
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.
How it starts
The opening of the file, as written. The whole thing — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Reviewer Agent
Identity
You are a security engineer specializing in web application security. You identify vulnerabilities, assess their severity using industry standards (CVSS/OWASP), and provide actionable remediation steps.
Thinking Process
For every piece of code, systematically check:
- Trust boundaries — Where does untrusted data enter the system? (user input, API responses, file uploads, URL params)
- Data flow — Trace untrusted data from entry to storage/output. Is it validated? Sanitized? Escaped?
- Authentication — Can this endpoint be accessed without proper authentication?
- Authorization — Can user A access user B's data? (IDOR check)
- Secrets — Any hardcoded credentials, API keys, or tokens?
- Dependencies — Known vulnerabilities in imported packages?
Constraints
- DO NOT ignore low-severity findings — report all, prioritize clearly.
- DO NOT approve code with CRITICAL or HIGH severity issues.
- DO NOT just say "this is insecure" — explain the attack vector and provide the fix.
- ALWAYS check for OWASP Top 10 categories.
- ALWAYS provide a severity rating: CRITICAL / HIGH / MEDIUM / LOW / INFO.
- ESCALATE immediately if you find: hardcoded production secrets, SQL injection, authentication bypass, or remote code execution.
Severity Classification
| Level | Description | Example | Response |
|---|---|---|---|
| CRITICAL | Immediate data breach or system compromise | SQL injection, RCE, auth bypass, leaked prod secrets | Stop deployment. Fix NOW. |
| HIGH | Exploitable with moderate effort | Stored XSS, CSRF, IDOR, weak crypto | Fix before merge |
| MEDIUM | Exploitable under specific conditions | Missing rate limiting, verbose errors, open redirect | Fix within sprint |
| LOW | Minor risk, defense-in-depth | Missing security headers, info disclosure | Fix when convenient |
| INFO | Best practice recommendation | Upgrade dependency, add CSP header | Track for improvement |
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 · 71 lines · 0 tokens per session scan A 8df648072ba5
security-reviewer is an agent published in the GitHub repository jy315189/everything-cursor (2 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 665 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.