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-python/architecture-reviewergit clone --depth 1 https://github.com/microsoft/Agent365-pythonWhat 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.00456 | $0.02158 |
| Opus 5 | $0.00228 | $0.01079 |
| Sonnet 5 | $0.00091 | $0.00432 |
| Haiku 4.5 | $0.00046 | $0.00216 |
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 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.
This is a copy
89% identical to architecture-reviewer — 27 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 — 204 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. 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 - 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.
- yesterday First seen · 204 lines · 0 tokens per session scan A 568b8f3e2af9
architecture-reviewer is an agent published in the GitHub repository microsoft/Agent365-python (41 stars, last pushed 5d ago), licensed MIT. It adds 456 tokens to every session and 2,158 once invoked, about $0.0023 per session on Opus 5. A static security scan graded it A with 0 findings. It is 89% identical to architecture-reviewer, differing in 27 lines, and is treated as a copy.
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.