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 commands/llcoolblaze/claude-boris/security-scangit 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/commands/llcoolblaze/claude-boris/security-scan)<a href="https://agentmods.dev/commands/llcoolblaze/claude-boris/security-scan"><img src="https://agentmods.dev/badge/commands/llcoolblaze/claude-boris/security-scan.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.00017 | $0.01038 |
| Opus 5 | $0.00009 | $0.00519 |
| Sonnet 5 | $0.00003 | $0.00208 |
| Haiku 4.5 | $0.00002 | $0.00104 |
Grade A, and why
security-scan 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 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.
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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Scan
Scanning...
Dependency Vulnerabilities
!npm audit --json 2>/dev/null | jq -r '.metadata.vulnerabilities | to_entries | map(select(.value > 0)) | .[] | "\(.key): \(.value)"' 2>/dev/null || npm audit 2>/dev/null | head -30 || echo "Run npm install first"
Outdated Packages
!npm outdated 2>/dev/null | head -15 || echo ""
Hardcoded Secrets Check
!grep -rn --include="*.ts" --include="*.js" --include="*.tsx" --include="*.jsx" -E "(password|secret|api_key|apikey|token)['\"]?\s*[:=]\s*['\"][a-zA-Z0-9+/=]{8,}" src/ 2>/dev/null | head -10 || echo "No obvious secrets found in src/"
AWS Credentials
!grep -rn "AKIA[0-9A-Z]{16}" . 2>/dev/null | head -5 || echo "No AWS keys found"
Private Keys
!find . -name "*.pem" -o -name "*.key" 2>/dev/null | grep -v node_modules | head -5 || echo "No private key files found"
SQL Injection Patterns
!grep -rn --include="*.ts" --include="*.js" -E "query\s*\(\s*['\"\].*\${" src/ 2>/dev/null | head -5 || echo "No obvious SQL injection patterns"`
Dangerous Functions
!grep -rn --include="*.ts" --include="*.js" -E "\beval\s*\(|new Function\s*\(" src/ 2>/dev/null | head -5 || echo "No eval/Function found"
XSS Vulnerabilities
!grep -rn --include="*.tsx" --include="*.jsx" "dangerouslySetInnerHTML" src/ 2>/dev/null | head -5 || echo "No dangerouslySetInnerHTML found"
CORS Configuration
!grep -rn --include="*.ts" --include="*.js" -E "cors.*['\"]\\*['\"]|Access-Control-Allow-Origin.*\\*" src/ 2>/dev/null | head -3 || echo "No wildcard CORS found"
Security Analysis
Invoke Security Auditor
For a complete analysis, invoke the security-auditor agent:
Use Task tool with subagent_type: security-auditor
The security auditor will:
- Run comprehensive SAST scans
- Check all OWASP Top 10 categories
- Analyze authentication flows
- Review authorization patterns
- Generate detailed report
Quick Fixes
High-Priority Actions
If vulnerabilities found:
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 · 140 lines · 17 tokens per session scan A c26ae0bccdcf
security-scan is a command published in the GitHub repository llcoolblaze/claude-boris (48 stars, last pushed 7mo ago), licensed MIT. It adds 17 tokens to every session and 1,038 once invoked, about $0.0001 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-30.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.