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/brennercruvinel/ccplugins/security-scangit clone --depth 1 https://github.com/brennercruvinel/CCPluginsWhat 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.00000 | $0.01136 |
| Opus 5 | $0.00000 | $0.00568 |
| Sonnet 5 | $0.00000 | $0.00227 |
| Haiku 4.5 | $0.00000 | $0.00114 |
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 3d 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 — 197 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Analysis
I'll perform comprehensive security analysis with tracking and remediation continuity across sessions.
Arguments: $ARGUMENTS - specific paths or security focus areas
Session Intelligence
I'll maintain security remediation progress:
Session Files (in current project directory):
security-scan/plan.md- All vulnerabilities and fixessecurity-scan/state.json- Remediation progress
IMPORTANT: Session files are stored in a security-scan folder in your current project root
Auto-Detection:
- If session exists: Show fixed vs pending vulnerabilities
- If no session: Perform new security scan
- Commands:
resume,status,new
Phase 1: Security Assessment
Extended Thinking for Security Analysis
For complex security scenarios, I'll use extended thinking to identify sophisticated vulnerabilities:
Triggers for Extended Analysis:
- Authentication and authorization systems
- Financial transaction processing
- Cryptographic implementations
- Multi-tenant architectures
- API security boundaries
MANDATORY FIRST STEPS:
- Check if
security-scandirectory exists in current working directory - If directory exists, check for session files:
- Look for
security-scan/state.json - Look for
security-scan/plan.md - If found, resume from existing session
- Look for
- If no directory or session exists:
- Perform full security scan
- Create vulnerability report
- Initialize tracking
- Show risk summary before remediation
Note: Always look for session files in the current project's security-scan/ folder, not ../../../security-scan/ or absolute paths
I'll analyze security across dimensions:
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.
- 3d ago First seen · 197 lines · 0 tokens per session scan A a2359939a051
security-scan is a command published in the GitHub repository brennercruvinel/CCPlugins (2,780 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,136 tokens. 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
README
Git workflow and quality assurance commands for the claude-skills repository.
convert-to-todowrite-tasklist-prompt
Purpose: Transform verbose, context-heavy slash commands into efficient TodoWrite tasklist-based methods with parallel subagent execution for 60-70% speed improvements.
security-audit
Perform a comprehensive security audit of the codebase to identify potential vulnerabilities, insecure patterns, and security best practice violations.
statusbar-style
Switch the status-bar style (classic / capsule / hairline).
hunt
Active vulnerability hunt against a target by invoking tools/hunt.py (which calls vulnscanner.sh against recon/ /). Auto-runs recon first if no recon dir exists. Usage: /hunt target.com.
writing:review
Exhaustive parallel editorial review of written content.