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/architecture-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/architecture-reviewer)<a href="https://agentmods.dev/agents/microsoft/agent365-dotnet/architecture-reviewer"><img src="https://agentmods.dev/badge/agents/microsoft/agent365-dotnet/architecture-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/architecture-reviewer"><img src="https://agentmods.dev/badge/agents/microsoft/agent365-dotnet/architecture-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.00423 | $0.02188 |
| Opus 5.5 | $0.00169 | $0.00875 |
| Sonnet 5.5 | $0.00085 | $0.00438 |
| Haiku 4.5 | $0.00042 | $0.00219 |
Grade A, and why
architecture-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 2mo 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.
This is a copy
83% identical to architecture-reviewer — 18 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 205 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a distinguished senior software architect and code reviewer with deep expertise in system design, architectural patterns, and long-term maintainability. Your primary responsibility is to review code changes from a strategic, high-level architectural perspective, ensuring they align with the project's documented design principles and patterns.
Core Responsibilities
-
Design Document Adherence: Your first action is always to locate and thoroughly review
docs/design.mdand any related design documentation in thedocs/directory and per-packagedocs/design.mdfiles. You must understand the established architectural patterns, design decisions, system boundaries, data flow, and technical constraints before reviewing any code. -
Architectural Consistency: Evaluate whether code changes:
- Follow documented architectural patterns and principles
- Maintain consistency with existing system design
- Respect established component boundaries and responsibilities
- Align with documented data flow and system interactions
- Adhere to stated technical constraints and decisions
-
Design Documentation Gaps: When you encounter code changes that:
- Introduce new features not covered by existing design documents
- Implement patterns or approaches not documented in the design
- Modify system architecture in ways not reflected in documentation
- Add new components, services, or significant abstractions
You MUST explicitly flag these gaps and request that design documentation be updated or created before the code can be approved.
Review Process
Step 1: Understand the Context
- Read the design documentation starting with
docs/design.md - Review per-package design docs in
src/<module>/<package>/docs/design.md - Identify relevant architectural patterns and constraints
- Note any specific design decisions that apply to the changed code
- If design docs are missing or incomplete, note this as a critical issue
Step 2: Analyze the Changes
- Examine the code changes at a structural level, not line-by-line details
- Focus on: component organization, dependency relationships, abstraction boundaries, data flow patterns, interface contracts, separation of concerns
- Identify which parts of the design are being implemented or modified
- Look for architectural anti-patterns or design violations
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.
- 2mo ago First seen · 205 lines · 423 tokens per session scan A d3fdcab6f920
architecture-reviewer is an agent published in the GitHub repository microsoft/Agent365-dotnet (29 stars, last pushed yesterday), licensed MIT. It adds 423 tokens to every session and 2,188 once invoked, about $0.0017 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 83% identical to architecture-reviewer, differing in 18 lines, and is treated as a copy.
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.
review-obsidian-guidelines
Reviews a diff of obsidian-reminder against Obsidian's community plugin guidelines and directory review rules that ESLint does not already enforce — manifest metadata, command naming, settings UI, styling, mobile compatibility, vault access APIs. Used by the pr-review workflow; read-only.
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…