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.
git clone --depth 1 https://github.com/rohittcodes/claude-plugin-suiteWrote 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/rohittcodes/claude-plugin-suite/security-scan)<a href="https://agentmods.dev/commands/rohittcodes/claude-plugin-suite/security-scan"><img src="https://agentmods.dev/badge/commands/rohittcodes/claude-plugin-suite/security-scan/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/commands/rohittcodes/claude-plugin-suite/security-scan"><img src="https://agentmods.dev/badge/commands/rohittcodes/claude-plugin-suite/security-scan.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.00007 | $0.00328 |
| Opus 5.5 | $0.00003 | $0.00131 |
| Sonnet 5.5 | $0.00001 | $0.00066 |
| Haiku 4.5 | $0.00001 | $0.00033 |
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 1mo 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
Security Scan Command
Perform comprehensive security scan and vulnerability assessment with detailed reporting.
Context
- Scan type: $1 (dependencies|code|infrastructure|all - default: all)
- Severity level: $2 (low|medium|high|critical - default: medium)
- Current dependencies: @package.json
- Security configuration: @.securityrc
Security Scan Process
1. Dependency Scanning
- Check for known vulnerabilities
- Validate license compliance
- Identify outdated packages
- Assess supply chain risks
2. Code Analysis
- Static Application Security Testing (SAST)
- Secret detection and credential scanning
- Code quality and security patterns
- OWASP Top 10 compliance check
3. Infrastructure Security
- Configuration security validation
- Network security assessment
- Access control verification
- Compliance framework validation
4. Security Reporting
- Vulnerability assessment report
- Risk prioritization and scoring
- Remediation recommendations
- Compliance status summary
Security Standards
- OWASP Top 10 compliance
- Industry security best practices
- Regulatory compliance (GDPR, HIPAA, SOC 2)
- Internal security policies
Expected Outcome
- Comprehensive security assessment report
- Prioritized vulnerability list
- Detailed remediation guidance
- Compliance status validation
Critical Issues
If critical vulnerabilities found:
- Immediate notification to security team
- Emergency remediation plan
- Deployment halt recommendations
- Incident response procedures
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.
- 1mo ago First seen · 60 lines · 0 tokens per session scan A 877b0d7fc8d1
security-scan is a command published in the GitHub repository rohittcodes/claude-plugin-suite (29 stars, last pushed 1y ago), licensed MIT. It adds 7 tokens to every session and 328 once invoked, about $0.0000 per session on Opus 5.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-09-21.
security-scan compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| security-scanrohittcodes/claude-plugin-suite | Command | 29 | 1y ago | MIT | A | 7 | Claude Code |
| checklistgithub/spec-kit | Command | 150k | 3d ago | MIT | A | 13 | Claude Code |
| clarifygithub/spec-kit | Command | 150k | 3d ago | MIT | A | 27 | Claude Code |
| specifygithub/spec-kit | Command | 150k | 3d ago | MIT | A | 13 | Claude Code |
| analyzegithub/spec-kit | Command | 150k | 3d ago | MIT | A | 26 | Claude Code |
| convergegithub/spec-kit | Command | 150k | 3d ago | MIT | A | 35 | Claude Code |
| implementgithub/spec-kit | Command | 150k | 3d ago | MIT | A | 14 | Claude Code |