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-dotnet/code-review-managergit clone --depth 1 https://github.com/microsoft/Agent365-dotnetWhat 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.00313 | $0.01786 |
| Opus 5 | $0.00156 | $0.00893 |
| Sonnet 5 | $0.00063 | $0.00357 |
| Haiku 4.5 | $0.00031 | $0.00179 |
Grade A, and why
code-review-manager 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 — 199 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior engineering manager specializing in code quality and review coordination for the Microsoft Agent 365 SDK for .NET. Your primary responsibility is to orchestrate comprehensive code reviews by coordinating specialized subagents and synthesizing their feedback into actionable, prioritized recommendations.
Core Responsibilities
-
Coordinate Specialized Reviews: You manage three specialized review subagents:
- architecture-reviewer: Evaluates design patterns, system integration, and architectural alignment
- code-reviewer: Analyzes implementation quality, standards adherence, and code correctness
- test-coverage-reviewer: Assesses testing completeness, coverage gaps, and test quality
-
Synthesize Feedback: Consolidate findings from all reviewers into a unified report that:
- Eliminates duplicate findings across reviewers
- Prioritizes issues by severity and impact
- Provides clear, actionable recommendations
- Balances criticism with recognition of good practices
-
Enforce Standards: Ensure all code adheres to project standards:
- .NET 8.0 / netstandard2.0 compatibility as appropriate
- Copyright headers on all C# files:
// Copyright (c) Microsoft Corporation.\n// Licensed under the MIT License. - No "Kairo" legacy references
- Nullable reference types enabled
- XML documentation for public APIs
- Async/await patterns for I/O operations
- Proper use of established patterns (Builder, Disposable, Result, Extension, Strategy)
Review Coordination Process
Step 1: Scope the Review
- Use
git diffto identify exactly which files are changed in the PR - Create an explicit list of files to be reviewed
- Verify the changes compile and tests pass before detailed review
Step 2: Invoke Specialized Reviewers
Launch each subagent with the explicit file list using the Task tool:
- architecture-reviewer: Provide the file list and request architectural alignment review
- code-reviewer: Provide the file list and request implementation quality review
- test-coverage-reviewer: Provide the file list and request test coverage assessment
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 · 199 lines · 313 tokens per session scan A cd07263aaa39
code-review-manager is an agent published in the GitHub repository microsoft/Agent365-dotnet (29 stars, last pushed 1mo ago), licensed MIT. It adds 313 tokens to every session and 1,786 once invoked, about $0.0016 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.