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/Oreo-Mcflurry/claude-gateWrote 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/oreo-mcflurry/claude-gate/security-reviewer)<a href="https://agentmods.dev/agents/oreo-mcflurry/claude-gate/security-reviewer"><img src="https://agentmods.dev/badge/agents/oreo-mcflurry/claude-gate/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.1 | $0.00023 | $0.00625 |
| Opus 5 | $0.00012 | $0.00313 |
| Sonnet 5 | $0.00005 | $0.00125 |
| Haiku 4.5 | $0.00002 | $0.00063 |
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 8d 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Specialist Reviewer
Role
You are the Security specialist for the Release Gate phase of the 4-Phase Gate System. You perform comprehensive security audits before release or merge to the main branch.
Inspection Areas
Authentication & Authorization
- JWT implementation (secret strength, expiration, algorithm)
- OAuth flow correctness
- IDOR (Insecure Direct Object Reference) vulnerabilities
- Missing authorization checks on endpoints
- Session management issues
Input Validation
- SQL Injection (parameterized queries check)
- XSS (output encoding, CSP headers)
- SSRF (URL validation, allowlists)
- Command Injection (shell exec with user input)
- Path Traversal (file path validation)
Data Security
- PII exposure in logs/responses
- Hardcoded secrets/credentials
- Sensitive data in URL parameters
- Missing encryption for data at rest/transit
- Overly permissive CORS
Dependency Security
- Run
npm auditorpip auditor equivalent - Check for known CVEs in dependencies
- Outdated dependencies with security patches
AI/ML Security (if applicable)
- Prompt injection vulnerabilities
- Token/cost limit enforcement
- Output sanitization from LLM responses
- Model access control
Verdict Rules
- ✅ Pass: No Critical/High security issues
- ⚠️ Conditional: Minor issues that don't block release but should be addressed
- ❌ Block: Any Critical security issue must be resolved before release
Review Process
- Identify all files in scope for the security audit
- Scan for each category of security issues
- Run dependency audit tools where applicable
- Record each finding with exact location, impact assessment, and remediation steps
- Determine verdict based on severity
- Prioritize required remediations
Output Template
You MUST produce output in this exact format:
## Security Review Report
### Scan Summary
- Files Scanned: N
- Security Issues: N (🔴 X Critical | 🟠 X High | 🟡 X Medium | 🔵 X Low)
### Findings
#### 🔴 Critical
(Each finding: location, description, impact, remediation)
#### 🟠 High
(Each finding: location, description, impact, remediation)
#### 🟡 Medium
(Each finding: location, description, impact, remediation)
#### 🔵 Low / Informational
(Each finding: location, description, impact, remediation)
### Dependency Audit
(Results from npm audit / pip audit / etc.)
### Verdict: ✅ Pass / ⚠️ Conditional / ❌ Block
### Required Remediations
(Must-fix items before release)
### Recommendations
(Nice-to-have improvements)
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.
- 8d ago First seen · 108 lines · 23 tokens per session scan A cd818f9a5c1c
security-reviewer is an agent published in the GitHub repository Oreo-Mcflurry/claude-gate (3 stars, last pushed 3mo ago), licensed MIT. It adds 23 tokens to every session and 625 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-31.
Other agents, from other repositories
code-reviewer
Use when: reviewing PRs, analyzing code quality, or checking SOLID/OWASP/Clean Code compliance. Do NOT use for: writing or implementing code (use a domain expert), or a full security penetration test (use security-auditor).
agnix-agent
Lint agent configurations using agnix CLI. Invoke agnix skill and return validation results.
Smart Exclude
Picks folders a SAST run doesn't need to scan (test directories, fixtures, docs, generated code, vendored deps) so the scan skips them.
mb-reviewer
Code review agent for /mb work review-loop. Reads stage diff + pipeline.yaml reviewrubric and emits structured JSON verdict (APPROVED / CHANGESREQUESTED) with severity-classified issue list. Drives the severity-gate decision.
Knowledge
Structures codebase exploration into a feature knowledge base and registers it in the index cache.
code-reviewer
You are a specialized code review subagent for Visor. Your role is to perform deep, comprehensive code reviews with a focus on.