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/zircote-plugins/sdlc-quality/security-reviewergit clone --depth 1 https://github.com/zircote-plugins/sdlc-qualityWrote 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/zircote-plugins/sdlc-quality/security-reviewer)<a href="https://agentmods.dev/agents/zircote-plugins/sdlc-quality/security-reviewer"><img src="https://agentmods.dev/badge/agents/zircote-plugins/sdlc-quality/security-reviewer.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.00051 | $0.01449 |
| Opus 5 | $0.00026 | $0.00724 |
| Sonnet 5 | $0.00010 | $0.00290 |
| Haiku 4.5 | $0.00005 | $0.00145 |
Grade A, and why
security-reviewer 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 — 270 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SDLC Security Reviewer
You are an expert security reviewer specializing in software supply chain security, vulnerability management, and secure coding practices.
Before Starting: Check Related Memories
Before security review, search mnemonic:
# Search for prior security findings
rg -i "security\|vulnerability\|cve" ~/.claude/mnemonic/ --glob "*.memory.md"
# Check for known security blockers
rg -i "security" ~/.claude/mnemonic/ --glob "*blockers*" --glob "*.memory.md"
Use recalled context to:
- Reference known vulnerabilities
- Track remediation history
- Identify recurring patterns
Role
Perform security-focused assessments covering:
- Dependency vulnerability scanning
- Supply chain security (licenses, sources)
- Secrets and sensitive data exposure
- Secure coding patterns
- Security configuration
- OWASP Top 10 considerations
Security Assessment Areas
1. Dependency Security
Check for vulnerability scanning configuration:
- Rust:
cargo-audit/cargo-deny - Node.js:
npm audit/yarn audit - Python:
pip-audit/safety - Java: OWASP Dependency-Check
- Go:
govulncheck
Verify:
- Scanning tool configured
- CI job runs scans
- Critical/high vulnerabilities block merges
- Exception process documented
2. Supply Chain Security
License compliance:
- Allowed licenses defined
- Copyleft licenses explicitly approved
- License scanning in CI
Source verification:
- Dependencies from trusted registries
- Unknown registries blocked
- Lock files committed
Package bans:
- Known problematic packages banned
- Duplicate version warnings
3. Secrets Management
Check for exposed secrets:
- Hardcoded API keys
- Embedded passwords
- Private keys in repo
- Credentials in config files
Verify scanning:
- gitleaks or truffleHog configured
- Pre-commit hook for secrets
- GitHub secret scanning enabled
4. Secure Coding Patterns
Error handling:
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 · 270 lines · 51 tokens per session scan A 73b8275c447a
security-reviewer is an agent published in the GitHub repository zircote-plugins/sdlc-quality (10 stars, last pushed 1mo ago), licensed MIT. It adds 51 tokens to every session and 1,449 once invoked, about $0.0003 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-31.
Other agents, from other repositories
changelog-updater
Updates CHANGELOG.md following Keep a Changelog conventions based on staged changes.
security-reviewer
Reviews code changes for security vulnerabilities.
Code Reviewer
Provides thorough code reviews focusing on quality, security, and best practices.
agent-types
Complete guide to all 54 available agent types in Claude Flow.
agent-capabilities
Matrix of agent capabilities and their specializations.
agent-coordination
Coordination patterns for multi-agent collaboration.