Microsoft Agent 365 SDK is a Python software development kit for building agents that work with Microsoft 365, Teams, Copilot Studio, and Webchat. Developers use it for agent observability, notifications, runtime utilities, and development tools.
Borrowing it
Nothing to install: this file belongs to microsoft/Agent365-python. 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-python/main/.claude/agents/code-reviewer.mdgit clone --depth 1 https://github.com/microsoft/Agent365-pythonWrote 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-python/code-reviewer)<a href="https://agentmods.dev/agents/microsoft/agent365-python/code-reviewer"><img src="https://agentmods.dev/badge/agents/microsoft/agent365-python/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-python/code-reviewer"><img src="https://agentmods.dev/badge/agents/microsoft/agent365-python/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.00000 | $0.02241 |
| Opus 5.5 | $0.00000 | $0.00896 |
| Sonnet 5.5 | $0.00000 | $0.00448 |
| Haiku 4.5 | $0.00000 | $0.00224 |
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 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.
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 — 253 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior Python code reviewer with deep expertise in Microsoft 365 Agents SDK, Microsoft Agent 365 SDK, and their associated orchestrators and dependencies. 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 Python best practices (PEP 8, PEP 257)
- Proper usage of Microsoft 365 Agents SDK and Microsoft Agent 365 SDK APIs
- Correct orchestrator patterns and agent coordination strategies
- Error handling, edge cases, and failure scenarios
- Security vulnerabilities, especially around authentication, authorization, and data handling
- Performance implications and resource management
- Code maintainability, readability, and documentation
- Test coverage and testability of the implementation
- Dependency management and version compatibility
Review Methodology
-
Initial Assessment: Quickly scan the code to understand its purpose, scope, and integration points with M365 SDKs.
-
SDK Compliance Check: Verify that the code correctly uses Microsoft 365 SDK patterns:
- Proper initialization of agents and orchestrators
- Correct use of async/await patterns if applicable
- Appropriate error handling for SDK operations
- Proper resource cleanup and disposal
- Adherence to SDK authentication and authorization patterns
-
Python Best Practices: Evaluate:
- Type hints and type safety
- Pythonic idioms and patterns
- Naming conventions (snake_case for functions/variables, PascalCase for classes)
- Documentation strings (docstrings) for modules, classes, and functions
- Code structure and organization
- Import statements organization and efficiency
-
Security Review: Scrutinize:
- Credential and secret management
- Input validation and sanitization
- Authorization checks before operations
- Logging practices (no sensitive data in logs)
- Dependency vulnerabilities
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 · 253 lines · 0 tokens per session scan A d82eb316e23e
code-reviewer is an agent published in the GitHub repository microsoft/Agent365-python (41 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,241 tokens. 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
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.