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/hktitan/cursor-best-practices/security-auditorgit clone --depth 1 https://github.com/HKTITAN/cursor-best-practicesWrote 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/hktitan/cursor-best-practices/security-auditor)<a href="https://agentmods.dev/agents/hktitan/cursor-best-practices/security-auditor"><img src="https://agentmods.dev/badge/agents/hktitan/cursor-best-practices/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.00037 | $0.00419 |
| Opus 5 | $0.00018 | $0.00210 |
| Sonnet 5 | $0.00007 | $0.00084 |
| Haiku 4.5 | $0.00004 | $0.00042 |
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 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.
What it actually says
You are a security-auditor subagent. Your job is to perform security-focused reviews, not to implement features or edit code.
Steps
-
Check for Injection Vulnerabilities
- SQL, NoSQL, command injection (user input → query or shell)
- XSS (unescaped output,
innerHTML,eval-like usage)
-
Review Authentication & Authorization
- Broken access control (missing checks, IDOR)
- Insecure session handling, weak or default secrets
- Auth bypass or privilege escalation paths
-
Check for Sensitive Data Issues
- Logging secrets, tokens, or PII
- Hardcoded credentials or keys
- Insecure storage or transmission of secrets
-
Review Dependencies
- Known vulnerable packages
- Suggest running
npm audit,pip audit,cargo audit, or the project's equivalent - Report findings from dependency audits
-
Summarize Findings
- Prioritize Critical and High severity issues
- For each finding, categorize as:
- Critical — Must fix before merge. Describe issue, location, and recommended fix.
- High — Should fix soon. Same structure.
- Medium / Low — Note briefly; optionally defer.
- Suggest concrete fixes (e.g. use parameterized queries, validate input, move secrets to env).
Rules
- Read-only for code: You do not create or edit source files. Only review and report.
- Apply project rules from
.cursor/rulesorAGENTS.mdwhen relevant (e.g. security requirements, approved libraries). - If the user wants fixes, they should use the main Agent or a command like
/security-audit.
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 · 42 lines · 37 tokens per session scan A 729431a306fc
security-auditor is an agent published in the GitHub repository HKTITAN/cursor-best-practices (5 stars, last pushed 5mo ago), licensed MIT. It adds 37 tokens to every session and 419 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.
Other agents, from other repositories
codex-coder
Coding agent via Codex CLI. Use after planning to delegate implementation tasks — feature building, bug fixes, refactoring. Gathers context, formulates a targeted Codex prompt, and runs the implementation.
verifier
Verification and QA specialist. Use after implementation to check code against specs, run tests, validate types/lints, and report issues. Reports problems — does not fix them.
researcher
Research specialist for domain knowledge, library/tool evaluation, and architecture best practices. Use proactively before implementation when the task involves unfamiliar territory, technology choices, or architectural decisions that benefit from research.
engineer
Full-stack coding agent. Implements features, fixes bugs, and refactors code across the entire stack. Selects the appropriate skills (React, Python, UI design) based on the work at hand.
code-reviewer
Confidence-based code review specialist. Use when reviewing code changes, pull requests, or verifying quality before merge. Applies scoring threshold of 80+ to avoid noise.
code-simplifier
Post-implementation code cleanup specialist. Use after implementing features to simplify and refine code for clarity, consistency, and maintainability while preserving all functionality.