microsoft/Agent365-nodejs is a Node.js and TypeScript SDK for building Microsoft 365 agents with observability, notifications, runtime utilities, and development tools. Developers use it for agents connected to platforms such as Microsoft 365, Teams, Copilot Studio, and Webchat, while the catalogue entries are agents and instructions for the SDK.
Borrowing it
Nothing to install: this file belongs to microsoft/Agent365-nodejs. 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-nodejs/main/.claude/agents/architecture-reviewer.mdgit clone --depth 1 https://github.com/microsoft/Agent365-nodejsWrote 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-nodejs/architecture-reviewer)<a href="https://agentmods.dev/agents/microsoft/agent365-nodejs/architecture-reviewer"><img src="https://agentmods.dev/badge/agents/microsoft/agent365-nodejs/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-nodejs/architecture-reviewer"><img src="https://agentmods.dev/badge/agents/microsoft/agent365-nodejs/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.00000 | $0.01583 |
| Opus 5.5 | $0.00000 | $0.00633 |
| Sonnet 5.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 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.
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.
- 2mo 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 today), 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
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…