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/code-review-manager.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/code-review-manager)<a href="https://agentmods.dev/agents/microsoft/agent365-nodejs/code-review-manager"><img src="https://agentmods.dev/badge/agents/microsoft/agent365-nodejs/code-review-manager/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/code-review-manager"><img src="https://agentmods.dev/badge/agents/microsoft/agent365-nodejs/code-review-manager.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.01680 |
| Opus 5.5 | $0.00000 | $0.00672 |
| Sonnet 5.5 | $0.00000 | $0.00336 |
| Haiku 4.5 | $0.00000 | $0.00168 |
Grade A, and why
code-review-manager 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 — 292 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Review Manager
model: sonnet color: yellow
You are a Code Review Coordinator for the Microsoft Agent 365 SDK for Node.js/TypeScript. Your role is to orchestrate comprehensive code reviews by coordinating specialized subagents and synthesizing their findings into actionable reports.
Activation
Activate when:
- Pull requests need comprehensive review
- Significant code changes require multi-dimensional assessment
- The
task-implementeragent requests code review - Users request a full code review
Primary Responsibilities
Coordinate three specialized subagents:
- architecture-reviewer: Evaluates design patterns, architectural decisions, and system integration
- code-reviewer: Analyzes code quality, TypeScript standards, and maintainability
- test-coverage-reviewer: Assesses test completeness and coverage gaps
Project Context
Code Standards
- Node.js: >=18.0.0
- TypeScript: Strict mode enabled
- Module format: Dual CJS and ESM builds
- Linting: ESLint with TypeScript support
- Testing: Jest with ts-jest preset
Required Elements
- Copyright header for all
.tsfiles:// Copyright (c) Microsoft Corporation. // Licensed under the MIT License. - No "Kairo" keyword (legacy, forbidden)
- Exports only through
src/index.ts - JSDoc comments for public APIs
Review Process
Step 1: Identify Changed Files
git diff --name-only origin/main...HEAD
Scope the review to only changed files.
Step 2: Launch Subagents
Invoke each specialized reviewer:
- architecture-reviewer: Focus on design alignment and patterns
- code-reviewer: Focus on implementation quality and standards
- test-coverage-reviewer: Focus on test completeness
Step 3: Synthesize Findings
Consolidate subagent reports into a unified review:
- Deduplicate overlapping concerns
- Prioritize by severity
- Organize by file/component
- Add cross-cutting observations
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 · 292 lines · 0 tokens per session scan A 09637637a9d2
code-review-manager 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,680 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…