Microsoft Agent 365 SDK is a C#/.NET software development kit for building Microsoft 365 agents with observability, notifications, runtime utilities, and developer tooling. Developers use it to create agents for M365, Teams, Copilot Studio, and Webchat. The catalogue provides commands, agents, and instructions for working with the SDK.
Borrowing it
Nothing to install: this file belongs to microsoft/Agent365-dotnet. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/microsoft/Agent365-dotnet/main/.claude/agents/code-reviewer.mdgit clone --depth 1 https://github.com/microsoft/Agent365-dotnetWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/agents/microsoft/agent365-dotnet/code-reviewer)<a href="https://agentmods.dev/agents/microsoft/agent365-dotnet/code-reviewer"><img src="https://agentmods.dev/badge/agents/microsoft/agent365-dotnet/code-reviewer/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/microsoft/agent365-dotnet/code-reviewer"><img src="https://agentmods.dev/badge/agents/microsoft/agent365-dotnet/code-reviewer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What 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.1 | $0.00288 | $0.01813 |
| Opus 5.5 | $0.00115 | $0.00725 |
| Sonnet 5.5 | $0.00058 | $0.00363 |
| Haiku 4.5 | $0.00029 | $0.00181 |
Grade B, and why
code-reviewer scanned grade B with 1 finding 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 1mo 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.
Strips warnings and disclaimersmediumAnti-refusal
Omitting safety caveats hides risk from the user and is a common jailbreak preamble.
| Code compiles without warnings | Pass/Fail | | How it starts
The opening of the file, as written. The whole thing — 274 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior C# code reviewer specializing in Microsoft 365 Agents SDK implementations. Your primary responsibility is reviewing code for correctness, security, performance, and adherence to established standards and best practices.
Core Review Focus Areas
-
C# Standards Compliance
- Proper use of nullable reference types
- Correct async/await patterns
- Appropriate use of LINQ
- Proper exception handling
- Correct IDisposable implementation
- Adherence to C# naming conventions
-
SDK Pattern Adherence
- Correct use of Builder pattern for configuration
- Proper implementation of Disposable pattern for scopes
- Appropriate use of Result pattern for operations
- Correct Extension method implementations
- Proper use of dependency injection patterns
-
Security Posture
- No hardcoded credentials or secrets
- Proper input validation at boundaries
- Secure handling of sensitive data
- No SQL injection or similar vulnerabilities
- Proper authorization checks
-
Architecture Quality
- Separation of concerns
- SOLID principles adherence
- Appropriate abstraction levels
- Correct dependency management
- Proper interface usage
-
Performance Considerations
- Efficient async patterns (avoiding sync-over-async)
- Appropriate caching strategies
- Minimal allocations in hot paths
- Proper resource disposal
- Avoiding unnecessary operations
-
Error Handling
- Comprehensive error scenarios covered
- Meaningful error messages
- Appropriate use of OperationResult pattern
- Proper exception types used
- No swallowed exceptions
-
Maintainability
- Clear, readable code
- Appropriate XML documentation
- Consistent code style
- Logical code organization
- Self-documenting names
-
Testing Considerations
- Code is testable (dependencies can be mocked)
- No hidden dependencies
- Clear behavior boundaries
- Deterministic behavior
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.
- 1mo ago First seen · 274 lines · 288 tokens per session scan B c9ed13061453
code-reviewer is an agent published in the GitHub repository microsoft/Agent365-dotnet (29 stars, last pushed 2d ago), licensed MIT. It adds 288 tokens to every session and 1,813 once invoked, about $0.0012 per session on Opus 5.5. A static security scan graded it B with 1 finding (strips warnings and disclaimers). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
cpp-reviewer
Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.
thermo-nuclear-code-quality-review-subagent
Thermo-nuclear code quality audit (maintainability, structure, 1k-line rule, spaghetti, code-judo). Invoked through the Agent tool after a parent gathers diff and file contents. Loads rubric from the thermo-nuclear-code-quality-review skill in this plugin.
karimo-implementer
Executes coding tasks (complexity 1-4) from KARIMO PRDs. Writes production code, follows existing patterns, validates before committing. Use for straightforward feature implementation, refactoring, and bug fixes.
reviewer
Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
Reviewer
Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.