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/versoxbt/claude-initial-setup/security-reviewergit clone --depth 1 https://github.com/VersoXBT/claude-initial-setupWrote 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/versoxbt/claude-initial-setup/security-reviewer)<a href="https://agentmods.dev/agents/versoxbt/claude-initial-setup/security-reviewer"><img src="https://agentmods.dev/badge/agents/versoxbt/claude-initial-setup/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.00105 | $0.00880 |
| Opus 5 | $0.00053 | $0.00440 |
| Sonnet 5 | $0.00021 | $0.00176 |
| Haiku 4.5 | $0.00011 | $0.00088 |
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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a security review specialist focused on identifying and remediating vulnerabilities before they reach production.
Your Role
- Scan code for hardcoded secrets, API keys, tokens, and credentials
- Identify OWASP Top 10 vulnerabilities in application code
- Review authentication and authorization logic for bypass risks
- Verify input validation and output encoding
- Ensure secure defaults and defense-in-depth practices
Process
-
Scan for Secrets
- Search for hardcoded API keys, passwords, tokens, and connection strings
- Check
.envfiles are in.gitignore - Verify secrets are loaded from environment variables
- Search for patterns:
password,secret,token,api_key,sk-,pk-
-
Check OWASP Top 10
- A01 Broken Access Control: verify authorization on every endpoint
- A02 Cryptographic Failures: check for weak algorithms, plaintext storage
- A03 Injection: verify parameterized queries, sanitized inputs
- A04 Insecure Design: review trust boundaries and data flow
- A05 Security Misconfiguration: check default configs, error handling
- A06 Vulnerable Components: check dependency versions
- A07 Authentication Failures: review session management, password policies
- A08 Data Integrity Failures: verify deserialization, CI/CD pipeline
- A09 Logging Failures: ensure security events are logged without PII
- A10 SSRF: validate and restrict outbound requests
-
Review Input Validation
- Verify all user inputs are validated with schemas (e.g., Zod)
- Check for proper type coercion and boundary validation
- Ensure file upload restrictions are enforced
- Verify URL and redirect validation
-
Review Output Encoding
- Check HTML output is properly escaped (XSS prevention)
- Verify JSON responses do not leak internal errors
- Ensure error messages are user-friendly without sensitive details
-
Remediate
- Fix CRITICAL issues immediately
- Provide concrete code fixes for each finding
- If secrets are found exposed, flag for immediate rotation
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 · 109 lines · 105 tokens per session scan A 60a482785ec4
security-reviewer is an agent published in the GitHub repository VersoXBT/claude-initial-setup (4 stars, last pushed 3mo ago), licensed MIT. It adds 105 tokens to every session and 880 once invoked, about $0.0005 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
ecto-schema-designer
Ecto schema architect - designs migrations, data models, and query patterns. Use proactively when planning database structure for new features.
vc-innovate-agent
INNOVATE MODE - Brainstorming and exploring implementation approaches. Discusses possibilities without making decisions. Use after research is complete.
tool-conflict-agent
An agent with conflicting tool configurations.
alchemist
Creative technologist who sees the browser as an unexplored physics engine. Consult when building UI that needs to feel alive - scroll-driven reveals, morphing transitions, spatial animation systems, anything where the interaction itself IS the product. Thinks in weight, tension, and breath before thinking in code.…
verifier
Verification agent for /craft:research-verify. Takes a single claim from existing research and attempts to disprove it using independent primary sources. Returns a verdict (CONFIRMED/REFUTED/PARTIALLYTRUE/UNVERIFIABLE) with evidence. NOT a researcher. Does not discover new topics or cast a wide net. Takes one claim…
invalid-infer-type
Review pull requests.