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/waishnav/devspace/copilot-reviewergit clone --depth 1 https://github.com/Waishnav/devspaceWhat 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.00021 | $0.00153 |
| Opus 5 | $0.00010 | $0.00077 |
| Sonnet 5 | $0.00004 | $0.00031 |
| Haiku 4.5 | $0.00002 | $0.00015 |
Grade A, and why
copilot-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.
Copies of this mod
5 near-identical copies found in the catalogue:
- copilot-reviewer — 100% identical, 0 lines differ
- copilot-reviewer — 100% identical, 0 lines differ
- copilot-reviewer — 100% identical, 0 lines differ
- copilot-reviewer — 94% identical, 2 lines differ
- copilot-reviewer — 92% identical, 3 lines differ
What it actually says
Review the requested code path or diff without editing. Prioritize concrete bugs, behavior regressions, security issues, and missing tests over style preferences.
- Do not modify files.
- Lead with findings ordered by severity.
- Tie each finding to a specific file, symbol, or behavior.
- Ignore purely subjective style feedback unless it creates a maintenance risk.
- If no issue is found, say that clearly and mention any residual test or runtime risk.
Report:
findings:
evidence:
test_gaps:
residual_risk:
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 · 26 lines · 21 tokens per session scan A 2d9f35b8bb25
copilot-reviewer is an agent published in the GitHub repository Waishnav/devspace (4,390 stars, last pushed yesterday), licensed MIT. It adds 21 tokens to every session and 153 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
reviewer
Reviews code, plans, architecture risk, and test gaps without editing files.
risk-reviewer
Engineering risk review for backend, data, and infrastructure changes.
security-reviewer
Review changes for security vulnerabilities and trust-boundary issues.
doc-writer
Author and edit documentation FILES on disk (README, guides, changelogs, docs).
analyst
Analyze requirements, ambiguity, and hidden constraints.
critic
Challenges planner and main-agent conclusions before risky decisions.