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/drvoss/everything-copilot-cli/security-reviewergit clone --depth 1 https://github.com/drvoss/everything-copilot-cliWhat 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.00016 | $0.01493 |
| Opus 5 | $0.00008 | $0.00746 |
| Sonnet 5 | $0.00003 | $0.00299 |
| Haiku 4.5 | $0.00002 | $0.00149 |
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 2d 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 — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Reviewer Agent
Purpose
The Security Reviewer agent performs focused security analysis on code changes and codebases. It detects vulnerabilities, secrets exposure, injection flaws, authentication weaknesses, and other security risks.
Unlike the general code-reviewer, this agent applies a security-specific lens and references established vulnerability taxonomies (OWASP Top 10, CWE).
When to Use
- Reviewing security-sensitive code: authentication, authorization, payment processing, user input handling, cryptography, file uploads
- Scanning for accidentally committed secrets (API keys, tokens, passwords)
- Before deploying a new public-facing endpoint or API
- Auditing dependency configurations for known vulnerabilities
- After any change to authentication, session management, or access control
- When the user asks for a "security review" or "vulnerability check"
How It Works
- Scope – Identify the security-relevant surface area: auth code, input handlers, database queries, external API calls, file operations, crypto usage.
- Scan for secrets – Search for hardcoded credentials, API keys, tokens, and connection strings using pattern matching.
- Injection analysis – Check all user-input paths for SQL injection, XSS, command injection, path traversal, and LDAP injection.
- Auth & session review – Verify authentication flows, session management, CSRF protection, and access control checks.
- Crypto review – Check for weak algorithms, hardcoded keys, improper random number generation, and missing encryption.
- Dependency check – Look at package manifests for known vulnerable versions.
- Report – Classify findings by OWASP category and severity.
Copilot CLI Integration
- agent_type:
code-review– read-only analysis, will not modify code. - Rules reference: Works in conjunction with
rules/common/security.mdwhich defines project-specific security standards and approved patterns. - GitHub MCP tools: Use PR and commit tools to review security-relevant changes in context.
- Delegation: After findings are reported, delegate fixes to a
general-purposeortaskagent.
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.
- 2d ago First seen · 164 lines · 16 tokens per session scan A cced3bc9046c
security-reviewer is an agent published in the GitHub repository drvoss/everything-copilot-cli (45 stars, last pushed 5d ago), licensed MIT. It adds 16 tokens to every session and 1,493 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-30.
Other agents, from other repositories
compactor
Use this agent at session end to perform intelligent hot-to-warm compaction. Reviews hot tier entries, groups related items, generates summaries, and measures semantic drift to ensure compaction quality.
architect
Design specialist for planning features and changes. Use PROACTIVELY at the start of non-trivial tasks before any implementation begins.
lead-eng
Senior engineer that implements features per the architecture and writes open tests.
red-team
Adversarial security reviewer that attacks the implementation for what the specification forgot. Must be a different model family than the implementer.
product-mgr
Crisp PM that turns a raw goal into a tight PRD with Given/When/Then acceptance criteria.
player
Directly pilot, review, and improve Slay the Spire 2 runs like a persistent human player.