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/llcoolblaze/claude-boris/security-auditorgit 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.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.00042 | $0.01970 |
| Opus 5 | $0.00021 | $0.00985 |
| Sonnet 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 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.
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.
- 5d 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 (48 stars, last pushed 7mo ago), licensed MIT. It adds 42 tokens to every session and 1,970 once invoked, about $0.0002 per session on Opus 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.