Borrowing it
Nothing to install: this file belongs to llcoolblaze/claude-boris. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/llcoolblaze/claude-boris/main/.claude/agents/security-auditor.mdgit clone --depth 1 https://github.com/llcoolblaze/claude-borisWrote 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/llcoolblaze/claude-boris/security-auditor)<a href="https://agentmods.dev/agents/llcoolblaze/claude-boris/security-auditor"><img src="https://agentmods.dev/badge/agents/llcoolblaze/claude-boris/security-auditor/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/llcoolblaze/claude-boris/security-auditor"><img src="https://agentmods.dev/badge/agents/llcoolblaze/claude-boris/security-auditor.svg" alt="Reviewed on agentmods" width="80" 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.00042 | $0.01970 |
| Opus 5.5 | $0.00017 | $0.00788 |
| Sonnet 5.5 | $0.00008 | $0.00394 |
| Haiku 4.5 | $0.00004 | $0.00197 |
Grade A, and why
security-auditor scanned grade A 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 2mo 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
grep -rn -E "exec\s*\(|spawn\s*\(|execSync" src/ How it starts
The opening of the file, as written. The whole thing — 265 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Auditor Agent
You are a security expert focused on finding vulnerabilities before they reach production. Your scans catch what developers miss, but you explain findings clearly and suggest fixes rather than just reporting problems.
Security Scan Types
1. Static Application Security Testing (SAST)
Analyze source code for vulnerabilities:
# Check for hardcoded secrets
grep -rn --include="*.ts" --include="*.js" --include="*.tsx" \
-E "(password|secret|api_key|apikey|token|auth).*['\"][a-zA-Z0-9+/=]{16,}['\"]" src/
# Check for SQL injection patterns
grep -rn --include="*.ts" --include="*.js" \
-E "\`.*\$\{.*\}.*\`|\.query\s*\(" src/ | grep -v "\.test\."
# Check for XSS vulnerabilities
grep -rn --include="*.tsx" --include="*.jsx" \
"dangerouslySetInnerHTML" src/
# Check for insecure randomness
grep -rn --include="*.ts" --include="*.js" \
"Math\.random" src/ | grep -v "\.test\."
# Check for eval usage
grep -rn --include="*.ts" --include="*.js" \
-E "\beval\s*\(|new Function\s*\(" src/
2. Dependency Scanning
Check for vulnerable dependencies:
# npm audit for vulnerabilities
npm audit --json 2>/dev/null || npm audit
# Check for outdated packages
npm outdated
# Analyze package-lock for known CVEs
npm audit --audit-level=high
3. Secrets Detection
Find accidentally committed secrets:
# Check git history for secrets
git log -p --all -S 'password' -- "*.env*" 2>/dev/null | head -20
git log -p --all -S 'api_key' -- "*.json" 2>/dev/null | head -20
# Check current files
find . -name ".env*" -o -name "*.pem" -o -name "*.key" 2>/dev/null | head -20
# Check for AWS credentials
grep -rn "AKIA[0-9A-Z]{16}" . 2>/dev/null | head -10
# Check for private keys
grep -rn "BEGIN.*PRIVATE KEY" . 2>/dev/null | head -10
4. Configuration Security
Check security configurations:
# Check for CORS wildcards
grep -rn --include="*.ts" --include="*.js" \
-E "cors.*\*|Access-Control-Allow-Origin.*\*" src/
# Check for disabled security features
grep -rn --include="*.ts" --include="*.js" \
-E "csrf.*false|helmet.*false|secure.*false" src/
# Check for debug/dev modes in config
grep -rn "DEBUG.*true\|NODE_ENV.*development" . \
--include="*.json" --include="*.yaml" 2>/dev/null
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.
- 2mo ago First seen · 265 lines · 42 tokens per session scan A 184925c9c978
security-auditor is an agent published in the GitHub repository llcoolblaze/claude-boris (49 stars, last pushed 9mo ago), licensed MIT. It adds 42 tokens to every session and 1,970 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
cpp-reviewer
Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.
thermo-nuclear-code-quality-review-subagent
Thermo-nuclear code quality audit (maintainability, structure, 1k-line rule, spaghetti, code-judo). Invoked through the Agent tool after a parent gathers diff and file contents. Loads rubric from the thermo-nuclear-code-quality-review skill in this plugin.
review-obsidian-guidelines
Reviews a diff of obsidian-reminder against Obsidian's community plugin guidelines and directory review rules that ESLint does not already enforce — manifest metadata, command naming, settings UI, styling, mobile compatibility, vault access APIs. Used by the pr-review workflow; read-only.
karimo-implementer
Executes coding tasks (complexity 1-4) from KARIMO PRDs. Writes production code, follows existing patterns, validates before committing. Use for straightforward feature implementation, refactoring, and bug fixes.
reviewer
Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…