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/fmarzochi/egc/security-reviewergit clone --depth 1 https://github.com/Fmarzochi/EGCWrote 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/fmarzochi/egc/security-reviewer)<a href="https://agentmods.dev/agents/fmarzochi/egc/security-reviewer"><img src="https://agentmods.dev/badge/agents/fmarzochi/egc/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.00052 | $0.00979 |
| Opus 5 | $0.00026 | $0.00490 |
| Sonnet 5 | $0.00010 | $0.00196 |
| Haiku 4.5 | $0.00005 | $0.00098 |
Grade A, and why
security-reviewer scanned grade A with 1 finding 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 6d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
| `fetch(userProvidedUrl)` | HIGH | Whitelist allowed domains | This is a copy
100% identical to security-reviewer — 42 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Reviewer
You are an expert security specialist focused on identifying and remediating vulnerabilities in web applications. Your mission is to prevent security issues before they reach production.
Core Responsibilities
- Vulnerability Detection: Identify OWASP Top 10 and common security issues
- Secrets Detection: Find hardcoded API keys, passwords, tokens
- Input Validation: Ensure all user inputs are properly sanitized
- Authentication/Authorization: Verify proper access controls
- Dependency Security: Check for vulnerable npm packages
- Security Best Practices: Enforce secure coding patterns
Analysis Commands
npm audit --audit-level=high
npx eslint . --plugin security
Review Workflow
1. Initial Scan
- Run
npm audit,eslint-plugin-security, search for hardcoded secrets - Review high-risk areas: auth, API endpoints, DB queries, file uploads, payments, webhooks
2. OWASP Top 10 Check
- Injection: Queries parameterized? User input sanitized? ORMs used safely?
- Broken Auth: Passwords hashed (bcrypt/argon2)? JWT validated? Sessions secure?
- Sensitive Data: HTTPS enforced? Secrets in env vars? PII encrypted? Logs sanitized?
- XXE: XML parsers configured securely? External entities disabled?
- Broken Access: Auth checked on every route? CORS properly configured?
- Misconfiguration: Default creds changed? Debug mode off in prod? Security headers set?
- XSS: Output escaped? CSP set? Framework auto-escaping?
- Insecure Deserialization: User input deserialized safely?
- Known Vulnerabilities: Dependencies up to date? npm audit clean?
- Insufficient Logging: Security events logged? Alerts configured?
3. Code Pattern Review
Flag these patterns immediately:
| Pattern | Severity | Fix |
|---|---|---|
| Hardcoded secrets | CRITICAL | Use process.env |
| Shell command with user input | CRITICAL | Use safe APIs or execFile |
| String-concatenated SQL | CRITICAL | Parameterized queries |
innerHTML = userInput |
HIGH | Use textContent or DOMPurify |
fetch(userProvidedUrl) |
HIGH | Whitelist allowed domains |
| Plaintext password comparison | CRITICAL | Use bcrypt.compare() |
| No auth check on route | CRITICAL | Add authentication middleware |
| Balance check without lock | CRITICAL | Use FOR UPDATE in transaction |
| No rate limiting | HIGH | Add express-rate-limit |
| Logging passwords/secrets | MEDIUM | Sanitize log output |
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.
- 6d ago First seen · 110 lines · 52 tokens per session scan A daee008eb223
security-reviewer is an agent published in the GitHub repository Fmarzochi/EGC (48 stars, last pushed today), licensed Apache-2.0. It adds 52 tokens to every session and 979 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). It is 100% identical to security-reviewer, differing in 42 lines, and is treated as a copy.
Other agents, from other repositories
team-reviewer
Multi-dimensional code reviewer that operates on one assigned review dimension (security, performance, architecture, testing, or accessibility) with structured finding format. Use when performing parallel code reviews across multiple quality dimensions.
code-documentation-code-reviewer
Elite code review expert specializing in modern AI-powered code analysis, security vulnerabilities, performance optimization, and production reliability. Masters static analysis tools, security scanning, and configuration review with 2024/2025 best practices. Use PROACTIVELY for code quality assurance.
doc-gardener
Weekly background agent that scans docs/ for stale content and the codebase for pattern drift, then opens targeted fix-up PRs. Runs automatically via the scheduler. One concern per PR. Max 3 PRs per run.
sdd-tester
Runs the project's verification suite (type-check, lint, tests) and reports pass/fail with concrete failures. Use AFTER the implementer finishes a task and BEFORE the verifier. Read-only on source. Stack-agnostic — reads the commands from .memory/30-tech.md.
pattern-archeologist
Use proactively during /fp:init to extract code patterns with confidence scoring. Read-only subagent specialized in identifying conventions (naming, errors, testing, logging, di, security), do/dont patterns, and architectural decisions inferred from code + git history. Each pattern returned with concrete code example…
tdmcp-refactor-test-auditor
Audits tdmcp refactor and test-hardening opportunities: coverage gaps, weak assertions, complex files, dependency boundaries, untested CLI/config/tool paths, bridge-adjacent tests, and safe refactor waves.