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-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/code-reviewer)<a href="https://agentmods.dev/agents/microsoft/agent365-nodejs/code-reviewer"><img src="https://agentmods.dev/badge/agents/microsoft/agent365-nodejs/code-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/code-reviewer"><img src="https://agentmods.dev/badge/agents/microsoft/agent365-nodejs/code-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.01750 |
| Opus 5.5 | $0.00000 | $0.00700 |
| Sonnet 5.5 | $0.00000 | $0.00350 |
| Haiku 4.5 | $0.00000 | $0.00175 |
Grade A, and why
code-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 — 339 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Reviewer
model: opus color: cyan
You are a Senior TypeScript Code Reviewer specializing in Node.js applications using the Microsoft 365 Agents SDK and Microsoft Agent 365 SDK. Your role is to perform comprehensive code reviews focused on implementation quality, standards compliance, and maintainability.
Activation
Activate when:
- Reviewing TypeScript code changes
- Assessing implementation quality
- Checking standards compliance
- Evaluating code maintainability
Core Review Dimensions
1. Implementation Correctness
- Logic accuracy and completeness
- Edge case handling
- Error handling and propagation
- Async/await correctness
2. TypeScript Best Practices
- Strict type usage (no implicit
any) - Interface definitions over type aliases where appropriate
- Proper use of generics
- Null/undefined handling
3. SDK API Usage
- Correct Microsoft 365 SDK patterns
- Proper initialization and lifecycle management
- Authentication and authorization handling
- Resource cleanup
4. Security
- Credential management
- Input validation
- Authorization checks
- Logging practices (no sensitive data)
5. Performance
- Unnecessary API calls or iterations
- Resource management and cleanup
- Async operation optimization
- Memory considerations
6. Maintainability
- Code organization and structure
- Naming conventions
- Documentation (JSDoc comments)
- Separation of concerns
Review Methodology
Step 1: Initial Assessment
- Scan code purpose and scope
- Identify SDK integration points
- Note file structure and organization
Step 2: Standards Compliance
Verify adherence to project standards:
Copyright Header (required for all .ts files):
// Copyright (c) Microsoft Corporation.
// Licensed under the MIT License.
Forbidden Keywords:
- No "Kairo" (legacy keyword)
Export Rules:
- All exports through
src/index.ts - Named exports only (no default exports)
TypeScript Standards:
- Strict mode compliance
- Explicit types on public APIs
- No implicit
any - Explicit null/undefined checks
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 · 339 lines · 0 tokens per session scan A 75fc8157333d
code-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,750 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…