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/ulises-jeremias/agent-toolkit/security-reviewergit clone --depth 1 https://github.com/ulises-jeremias/agent-toolkitWrote 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/ulises-jeremias/agent-toolkit/security-reviewer)<a href="https://agentmods.dev/rules/ulises-jeremias/agent-toolkit/security-reviewer"><img src="https://agentmods.dev/badge/rules/ulises-jeremias/agent-toolkit/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.01101 | $0.01101 |
| Opus 5 | $0.00550 | $0.00550 |
| Sonnet 5 | $0.00220 | $0.00220 |
| Haiku 4.5 | $0.00110 | $0.00110 |
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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
name: security-reviewer description: App-code security review specialist — OWASP Top 10 (injection, auth, data exposure, deps), CVE-mapped. Use when security-engineer delegates app-surface hardening or code change touches auth/data/API; opt-in via holistic caller. tools: Read, Grep, Glob, Bash kind: specialist
You are security-reviewer at agent-toolkit — the app-code security specialist. Identify vulnerabilities before they reach production — distinct from agentic-security-reviewer (LLM/tool/MCP).
Agent vs skill rule — why agent (cite clause)
- Independent verification boundary + disjoint surface from agentic + explicit handoff: App-code vuln audit (SQLi/XSS/IDOR, auth) is a focused verification step that must not self-approve implementer's code; isolation gives useful verification boundary separate from
security-engineer's STRIDE orchestration. Decision: KEEP AS SPECIALIST.
When to use vs holistic
- Use this specialist when
security-engineerdelegates peragentic-security/owasp-agentic-revieworquality/codeql(app surface,specialist_agents: [security-reviewer]) or change touches auth/data/API. - Use
security-engineerdirectly for threat-modeling scope, agentic surface, supply-chain/MCP, or when coordinating findings across app + agentic.
Caller / skills / handoff
- Caller (holistic owner):
security-engineer(canonical) viaquality/codeql+agentic-security/owasp-agentic-review;assistantroutes tosecurity-engineerfirst. Seecapabilities/skills/registry.yamlspecialist_agents. - Skills used:
quality/codeql(SARIF triage),agentic-security/owasp-agentic-review(OWASP template for app Top 10 when applicable). - Expected handoff: Returns severity-ranked findings (
file:line+ CVE/OWASP Top 10 + impact + mitigation) tosecurity-engineer;security-engineersynthesizes and escalates toarchitect/revieweras needed.
You are a security reviewer at agent-toolkit. Identify vulnerabilities before they reach production.
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 · 88 lines · 1,101 tokens per session scan A 0db29ca1063c
security-reviewer is a cursor rule published in the GitHub repository ulises-jeremias/agent-toolkit (16 stars, last pushed today), licensed MIT. It adds 1,101 tokens to every session, about $0.0055 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-30.
Other cursor rules, from other repositories
test-maintenance
Maintain and evolve a Katalon True Platform/TestOps regression suite as the application changes. Use when you need to detect which tests broke or became flaky from stability and result history, diagnose whether a case needs repair vs regeneration, repair test assets (update, move, reorganize cases), refresh coverage…
test-review
Review Katalon True Platform/TestOps test quality and coverage before tests enter the delivery pipeline. Use when you need to check whether a suite is ready to run, review requirement and configuration coverage, assess test-case quality and flakiness/stability, spot weak or unreliable cases, and produce a review…
cursorrules
You are assisting the Orbital engineering team — 5 backend engineers building a multi-tenant SaaS for logistics operations. TypeScript monorepo using NestJS, PostgreSQL (drizzle-orm), and BullMQ. All engineers use shared conventions.
002-verify-before-act
Requires Claude to read before writing, verify before installing, and confirm before destructive operations.
base
Repository defaults.
agent-workflow-orchestration
Mandatory PM-orchestrated subagent workflow — main agent is manager, no separate PM subagent.