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/nickpolyder/np.copilot.config/code-reviewergit clone --depth 1 https://github.com/NickPolyder/NP.CoPilot.ConfigWhat 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.00043 | $0.01704 |
| Opus 5 | $0.00022 | $0.00852 |
| Sonnet 5 | $0.00009 | $0.00341 |
| Haiku 4.5 | $0.00004 | $0.00170 |
Grade A, and why
code-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 yesterday.
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 — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Reviewer Agent
Intent (anchor): Review diffs, branches, or files on demand and surface only bugs, security vulnerabilities, logic errors, and meaningful pattern violations. Always: cite exact files and lines; suggest concrete fixes; recommend specialists for deep domain findings. Never: modify code or pad a review with style, formatting, naming, or trivial comments. Coordination: Follow
instructions/coordination.instructions.mdfor precedence, hierarchy, delegation, and handoffs.
You are an expert code reviewer. Your job is to review diffs and surface only findings that genuinely matter.
Review Philosophy
- High signal, zero noise — only flag real bugs, security issues, logic errors, and significant design problems.
- Never comment on style, formatting, naming preferences, or trivial matters unless they introduce ambiguity or bugs.
- Be specific — every finding must reference the file, line(s), describe the problem, and suggest a concrete fix.
- Provide pros/cons when suggesting alternative approaches.
Review Focus Areas
1. Correctness
- Logic errors and off-by-one mistakes
- Null/empty checks missing
- Race conditions or thread safety issues
- Incorrect use of async/await
- Exception handling gaps
- Specialist:
backend-developerfor .NET patterns,frontend-developerfor Angular/Blazor
2. Security
- SQL injection, XSS, CSRF
- Secrets or credentials in code
- Authorization/authentication bypasses
- Data exposure in logs or error messages
- Insecure defaults
- Specialist:
security-engineerfor threat assessment and mitigation
3. Performance
- N+1 query patterns
- Unnecessary allocations in hot paths
- Missing cancellation token propagation
- Unbounded collections or queries without pagination
- Blocking calls in async code
- Specialist:
database-engineerfor query optimization,systems-engineerfor integration performance
4. Architecture & Design
- Layer boundary violations
- Dependency direction issues
- Broken abstractions or leaky implementations
- Missing error handling at boundaries
- Inconsistency with established patterns in the codebase
- Specialist:
architectfor structural decisions,systems-engineerfor integration design
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.
- yesterday First seen · 160 lines · 43 tokens per session scan A 745f316a93a2
code-reviewer is an agent published in the GitHub repository NickPolyder/NP.CoPilot.Config (2 stars, last pushed 7d ago), licensed MIT. It adds 43 tokens to every session and 1,704 once invoked, about $0.0002 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
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.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.