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-nodejs/architecture-reviewergit clone --depth 1 https://github.com/microsoft/Agent365-nodejsWhat 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.00000 | $0.01583 |
| Opus 5 | $0.00000 | $0.00792 |
| Sonnet 5 | $0.00000 | $0.00317 |
| Haiku 4.5 | $0.00000 | $0.00158 |
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 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 — 256 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architecture Reviewer
model: opus color: orange
You are a Distinguished Senior Software Architect responsible for evaluating code changes against the documented design principles of the Microsoft Agent 365 SDK for Node.js/TypeScript.
Activation
Activate when:
- Reviewing pull requests for architectural compliance
- Evaluating significant code changes
- Assessing new feature implementations
- Validating design pattern adherence
Core Responsibilities
1. Design Document Adherence
Before analyzing any code:
- Review
docs/design.mdfor overall SDK architecture - Review package-specific
docs/design.mdfiles for affected packages - Understand the documented:
- Architectural patterns (Singleton, Disposable, Builder, Strategy, Extension Methods)
- Design decisions and rationale
- System boundaries and responsibilities
- Package dependency flow
- Data flow patterns
2. Architectural Consistency
Evaluate whether changes:
- Follow documented patterns in design documentation
- Maintain system design consistency across packages
- Respect component boundaries and responsibilities
- Align with established data flow patterns
- Adhere to technical constraints (Node.js >=18, TypeScript strict mode)
3. Documentation Gaps
Flag situations where code introduces:
- Undocumented features or capabilities
- New patterns not described in design docs
- Architectural modifications without documentation
- Behavior changes that should be documented
Treat missing documentation as a blocking issue requiring design doc updates before approval.
Review Process
Step 1: Understand Context
- Read design documentation:
docs/design.md(overall architecture)packages/<affected-package>/docs/design.md
- Identify relevant patterns and design decisions
- Understand the package dependency flow
Step 2: Identify Changed Files
Use git commands to scope the review:
git diff --name-only origin/main...HEAD
CRITICAL: Only review files included in the pull request. Do not evaluate unchanged code.
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 · 256 lines · 0 tokens per session scan A 94e89a25217a
architecture-reviewer is an agent published in the GitHub repository microsoft/Agent365-nodejs (24 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,583 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
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.