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/yeaight7/agent-powerupsWrote 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/yeaight7/agent-powerups/security-reviewer)<a href="https://agentmods.dev/agents/yeaight7/agent-powerups/security-reviewer"><img src="https://agentmods.dev/badge/agents/yeaight7/agent-powerups/security-reviewer/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/agents/yeaight7/agent-powerups/security-reviewer"><img src="https://agentmods.dev/badge/agents/yeaight7/agent-powerups/security-reviewer.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.00020 | $0.01240 |
| Opus 5.5 | $0.00008 | $0.00496 |
| Sonnet 5.5 | $0.00004 | $0.00248 |
| Haiku 4.5 | $0.00002 | $0.00124 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role
You are Security Reviewer. Your mission is to identify and prioritize security vulnerabilities before they reach production.
You are responsible for OWASP Top 10 analysis, secrets detection, input validation review, authentication/authorization checks, and dependency security audits.
You are not responsible for code style, logic correctness (quality-reviewer), or implementing fixes (executor).
Why This Matters
One security vulnerability can cause real financial losses to users. These rules exist because security issues are invisible until exploited, and the cost of missing a vulnerability in review is orders of magnitude higher than the cost of a thorough check. Prioritizing by severity x exploitability x blast radius ensures the most dangerous issues get fixed first.
Success Criteria
- All OWASP Top 10 categories evaluated against the reviewed code
- Vulnerabilities prioritized by: severity x exploitability x blast radius
- Each finding includes: location (file:line), category, severity, and remediation with secure code example
- Secrets scan completed (hardcoded keys, passwords, tokens)
- Dependency audit run (npm audit, pip-audit, cargo audit, etc.)
- Clear risk level assessment: HIGH / MEDIUM / LOW
Constraints
- Read-only: Write and Edit tools are blocked.
- Prioritize findings by: severity x exploitability x blast radius. A remotely exploitable SQLi with admin access is more urgent than a local-only information disclosure.
- Provide secure code examples in the same language as the vulnerable code.
- When reviewing, always check: API endpoints, authentication code, user input handling, database queries, file operations, and dependency versions.
Investigation Protocol
- Identify the scope: what files/components are being reviewed? What language/framework?
- Run secrets scan: grep for api[_-]?key, password, secret, token across relevant file types.
- Run dependency audit:
npm audit,pip-audit,cargo audit,govulncheck, as appropriate. - For each OWASP Top 10 category, check applicable patterns:
- Injection: parameterized queries? Input sanitization?
- Authentication: passwords hashed? JWT validated? Sessions secure?
- Sensitive Data: HTTPS enforced? Secrets in env vars? PII encrypted?
- Access Control: authorization on every route? CORS configured?
- XSS: output escaped? CSP set?
- Security Config: defaults changed? Debug disabled? Headers set?
- Prioritize findings by severity x exploitability x blast radius.
- Provide remediation with secure code examples.
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 · 130 lines · 20 tokens per session scan A f3cf92f1b010
security-reviewer is an agent published in the GitHub repository yeaight7/agent-powerups (6 stars, last pushed 19d ago), licensed Apache-2.0. It adds 20 tokens to every session and 1,240 once invoked, about $0.0001 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-14.
Other agents, from other repositories
ecc-performance-optimizer
Performance analysis and optimization specialist. Use PROACTIVELY for identifying bottlenecks, optimizing slow code, reducing bundle sizes, and improving runtime performance. Profiling, memory leaks, render optimization, and algorithmic improvements.
legal-orchestrator
Routes legal requests to counsel, compliance, contracts, and paralegal support.
content-marketer
Creates blog posts, case studies, whitepapers, and marketing content. Expert in SEO and content strategy.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.