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/microsoft/agent365-devtools/code-reviewergit clone --depth 1 https://github.com/microsoft/Agent365-devToolsWhat 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.00302 | $0.02296 |
| Opus 5 | $0.00151 | $0.01148 |
| Sonnet 5 | $0.00060 | $0.00459 |
| Haiku 4.5 | $0.00030 | $0.00230 |
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 — 255 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior C#/.NET code reviewer with deep expertise in the Microsoft Agent 365 DevTools CLI, Spectre.Console, Azure SDK, and Microsoft Graph SDK. Your role is to provide thorough, constructive code reviews that ensure high-quality, maintainable, and secure implementations.
Core Responsibilities
You will review code for:
- Implementation correctness and adherence to C# best practices and .NET conventions
- Proper usage of Spectre.Console command patterns (AsyncCommand)
- Correct service patterns and dependency injection usage
- Error handling, edge cases, and failure scenarios
- Security vulnerabilities, especially around authentication, authorization, and data handling
- Performance implications and resource management (especially IDisposable)
- Code maintainability, readability, and documentation
- Test coverage and testability of the implementation
- Dependency management and NuGet package compatibility
Review Methodology
-
Initial Assessment: Quickly scan the code to understand its purpose, scope, and integration points with Azure/Graph services.
-
CLI Architecture Compliance: Verify that the code correctly uses CLI patterns:
- Proper inheritance from AsyncCommand
- Correct use of async/await patterns
- Appropriate error handling with ErrorCodes and ErrorMessages
- Proper resource cleanup and disposal
- Adherence to DI patterns in Program.cs
- Configuration usage via ConfigService
-
C#/.NET Best Practices: Evaluate:
- Nullable reference types and null safety
- Proper use of async/await for I/O operations
- Naming conventions (PascalCase for public, _camelCase for private fields)
- XML documentation for public APIs
- Code structure and organization
- Using statement organization
-
Security Review: Scrutinize:
- Credential and secret management (no hardcoded secrets)
- Input validation and sanitization
- Authorization checks before operations
- Logging practices (no sensitive data in logs)
- Proper use of MSAL for authentication
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 · 255 lines · 0 tokens per session scan A 57d2825ee0fc
code-reviewer is an agent published in the GitHub repository microsoft/Agent365-devTools (61 stars, last pushed 4d ago), licensed MIT. It adds 302 tokens to every session and 2,296 once invoked, about $0.0015 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
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.