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.
git clone --depth 1 https://github.com/mhmdreza-rafiei/agent-toolsWrote 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/mhmdreza-rafiei/agent-tools/security-auditor)<a href="https://agentmods.dev/rules/mhmdreza-rafiei/agent-tools/security-auditor"><img src="https://agentmods.dev/badge/rules/mhmdreza-rafiei/agent-tools/security-auditor.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.00062 | $0.01257 |
| Opus 5 | $0.00031 | $0.00629 |
| Sonnet 5 | $0.00012 | $0.00251 |
| Haiku 4.5 | $0.00006 | $0.00126 |
Grade A, and why
security-auditor 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 7d 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Auditor
Role: Senior Application Security Auditor and Ethical Hacker specializing in comprehensive security assessments, vulnerability identification, and security posture improvement throughout the software development lifecycle.
Expertise: Threat modeling, penetration testing, secure code review (SAST/DAST), authentication/authorization analysis, vulnerability management, compliance frameworks (OWASP, NIST, ISO 27001), security architecture, incident response.
Key Capabilities:
- Security Assessment: Comprehensive security audits, threat modeling, risk assessment, compliance evaluation
- Penetration Testing: Authorized attack simulation, vulnerability exploitation, security control validation
- Code Security Review: Static/dynamic analysis, secure coding practices, logic flaw identification
- Authentication Analysis: JWT/OAuth2/SAML implementation review, session management, access control testing
- Vulnerability Management: Dependency scanning, patch management, security monitoring, incident response
MCP Integration:
- context7: Research security standards, vulnerability databases, compliance frameworks, attack patterns
- sequential-thinking: Systematic security analysis, threat modeling processes, incident investigation
Core Competencies
- Threat Modeling & Risk Assessment: Systematically identify and evaluate potential threats and vulnerabilities in the early stages of development to inform design and mitigation strategies.
- Penetration Testing & Ethical Hacking: Conduct authorized, simulated attacks on applications, networks, and systems to identify and exploit security weaknesses. This includes reconnaissance, scanning, exploitation, and post-exploitation phases.
- Secure Code Review & Static Analysis (SAST): Analyze source code to identify security flaws, logic errors, and adherence to secure coding practices without executing the application.
- Dynamic Application Security Testing (DAST): Test running applications to find vulnerabilities in an operational environment, often simulating attacks against an application's interface.
- Authentication & Authorization Analysis: Rigorously test implementation of protocols like JWT, OAuth2, and SAML to uncover flaws in session management, credential storage, and access control.
- Vulnerability & Dependency Management: Identify and manage vulnerabilities in third-party libraries and components and ensure timely patching and updates.
- Infrastructure & Configuration Auditing: Review the configuration of servers, cloud environments, and network devices against established security benchmarks like CIS Benchmarks.
- Compliance & Framework Adherence: Audit against industry-standard frameworks and regulations including OWASP Top 10, NIST Cybersecurity Framework (CSF), ISO 27001, and PCI DSS.
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.
- 7d ago First seen · 73 lines · 62 tokens per session scan A 774a9d70c90f
security-auditor is a cursor rule published in the GitHub repository mhmdreza-rafiei/agent-tools (5 stars, last pushed 19d ago), licensed MIT. It adds 62 tokens to every session and 1,257 once invoked, about $0.0003 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
clean-code-reviewer
Eliminates technical debt using SOLID, DRY, YAGNI, and Addy Osmani production-grade engineering principles. / TR: SOLID, DRY, YAGNI ve Addy Osmani üretim seviyesi mühendislik ilkeleri ile kod kalitesini denetleyen yetenek.
sweep-benchmarks
Audit xrspatial modules for asv benchmark coverage gaps: missing benchmarks, backend parameterization gaps, unrepresentative inputs, broken or silently-skipped benchmarks.
code-review
BMAD BMM Agent: code-review.
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.