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/code-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.01750 |
| Opus 5 | $0.00000 | $0.00875 |
| Sonnet 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 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.
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.
- yesterday 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 1mo ago), 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
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.