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/afiqiqmal/claude-security-audit/security-auditgit clone --depth 1 https://github.com/afiqiqmal/claude-security-auditWrote 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/afiqiqmal/claude-security-audit/security-audit)<a href="https://agentmods.dev/rules/afiqiqmal/claude-security-audit/security-audit"><img src="https://agentmods.dev/badge/rules/afiqiqmal/claude-security-audit/security-audit.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.00073 | $0.09485 |
| Opus 5 | $0.00036 | $0.04743 |
| Sonnet 5 | $0.00015 | $0.01897 |
| Haiku 4.5 | $0.00007 | $0.00949 |
Grade B, and why
security-audit scanned grade B with 1 finding 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 4d 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.
Cloud metadata endpointmediumServer-side request forgery
One request to 169.254.169.254 can return temporary IAM credentials.
1. **Broken Access Control** [A01:2025 | PR.AA] - IDOR, privilege escalation, missing middleware, role bypass, horizontal/vertical access violations, CORS misconfiguration, metadata manipulation, SSRF (user-controlled UR Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 626 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Audit
You are an expert application security engineer. Perform a white-box and gray-box security audit on THIS project, scanning every attack surface. Map all findings to both OWASP Top 10:2025 and NIST Cybersecurity Framework (CSF) 2.0.
Mode Selection
Parse the audit mode and flags from the user's message. If no mode is specified, default to full.
- full (default if empty) - All phases: recon + white-box + gray-box + hotspots + smells (Phases 1-5)
- quick - CRITICAL and HIGH severity issues only across all white-box categories, skip gray-box, hotspots and smells (Phases 1-2 only)
- gray - Gray-box testing only: role-based access, API probing, credential boundaries, rate limits and error differentials (Phases 1 and 3 only)
- focus:auth - Deep dive on authentication and authorization (Phase 1 + Phase 2 categories A01, A07 + Phase 4 auth hotspots only)
- focus:api - Deep dive on API security, input validation and rate limiting (Phase 1 + Phase 2 categories A01, A05, A06 for APIs + Phase 4 input/output hotspots only)
- focus:config - Deep dive on configuration, supply chain and infrastructure (Phase 1 + Phase 2 categories A02, A03, A08 + Phase 4 config hotspots only)
- diff - Scan only files changed since last commit (
git diff HEAD), skip gray-box and smells (Phases 0, 1, 2, 4) - diff:BRANCH - Scan only files changed compared to a branch (e.g.,
diff:main), skip gray-box and smells (Phases 0, 1, 2, 4) - recheck:PATH - Re-audit specific files or directories (e.g.,
recheck:src/authorrecheck:src/auth,src/api). Runs Phase 1 (full recon for context) then Phase 2 + Phase 4 scoped to the specified paths only - triage - Interactive triage of an existing report. Requires
./security-audit-report.mdto exist. Walks through each finding and asks the developer to Accept, Defer, Dismiss or Escalate. Outputs./security-audit-triage.md - phase:1 - Reconnaissance only - map project structure, tech stack, entry points, data flow and custom checks
- phase:2 - White-box analysis only - run all 20 attack categories against the full codebase
- phase:3 - Gray-box testing only - role-based access, API probing, credential boundaries, rate limits, error differentials
- phase:4 - Security hotspots only - flag sensitive code areas that need careful review
- phase:5 - Code smells only - structural, data handling, error handling, dependency and design patterns
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.
- 4d ago First seen · 626 lines · 73 tokens per session scan B 6532edbfa971
security-audit is a cursor rule published in the GitHub repository afiqiqmal/claude-security-audit (22 stars, last pushed 6mo ago), licensed MIT. It adds 73 tokens to every session and 9,485 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it B with 1 finding (cloud metadata endpoint). 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
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.
family-instance-domain-actions
Family instance domain action implementation patterns.