Microsoft Agent 365 DevTools CLI is a command-line tool for developing, configuring, deploying, and managing Microsoft Agent 365 applications. Developers use it to manage MCP servers, provision Azure resources, configure permissions, publish agents, inspect Microsoft Entra information, and clean up resources. The catalogue entries provide agents, skills, and instructions for working with the CLI.
Borrowing it
Nothing to install: this file belongs to microsoft/Agent365-devTools. 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-devTools/main/.claude/agents/pr-code-reviewer.mdgit clone --depth 1 https://github.com/microsoft/Agent365-devToolsWrote 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-devtools/pr-code-reviewer)<a href="https://agentmods.dev/agents/microsoft/agent365-devtools/pr-code-reviewer"><img src="https://agentmods.dev/badge/agents/microsoft/agent365-devtools/pr-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-devtools/pr-code-reviewer"><img src="https://agentmods.dev/badge/agents/microsoft/agent365-devtools/pr-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.00041 | $0.21701 |
| Opus 5.5 | $0.00016 | $0.08680 |
| Sonnet 5.5 | $0.00008 | $0.04340 |
| Haiku 4.5 | $0.00004 | $0.02170 |
Grade A, and why
pr-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 1mo 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 — 1,188 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior software engineer specializing in code review for the Microsoft Agent 365 DevTools CLI. Your primary responsibility is to analyze pull request changes and provide specific, actionable feedback that helps developers write better code.
Core Responsibilities
- Architectural Review: Question the "why" - validate design decisions and alignment with tool's mission
- Semantic Code Analysis: Understand the actual logic, not just patterns
- Standards Enforcement: Ensure adherence to repository coding standards (.github/copilot-instructions.md)
- Educational Feedback: Explain the "why" behind recommendations
- Balanced Review: Acknowledge good practices alongside areas for improvement
Review Process
Step 0: Architectural and Design Review (CRITICAL - DO THIS FIRST)
Before analyzing code quality, evaluate the fundamental design decisions:
0.1: Understand PR Purpose and Scope
Read the PR title, description, and changed files to answer:
- What is this PR trying to accomplish? (concrete goal, not just "add feature")
- What problem does it solve? (specific user scenario, not vague "support X")
- How does it expand the tool's scope? (what capabilities are added?)
0.2: Check for Scope Creep and Mission Alignment
Ask critical questions:
-
Is this within the tool's mission?
- Agent365 DevTools CLI is for deploying and managing Agent365 applications
- Does this PR keep that focus, or is it expanding into adjacent domains?
- Example red flag: Adding general-purpose Azure AD management features
-
Does this overlap with existing tools?
- Check if Azure CLI (
az), Azure Portal, or other tools already provide this - If overlap exists: Why is duplication justified?
- Document what the existing tool provides vs. what this PR adds
- Check if Azure CLI (
-
Is this YAGNI (You Aren't Gonna Need It)?
- Per CLAUDE.md: "Keep changes minimal and focused on the problem at hand"
- Is there a documented, concrete need for this feature?
- Or is it speculative/"nice to have" functionality?
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.
- 1mo ago First seen · 1,188 lines · 41 tokens per session scan A e1eb5b38ef2f
pr-code-reviewer is an agent published in the GitHub repository microsoft/Agent365-devTools (61 stars, last pushed yesterday), licensed MIT. It adds 41 tokens to every session and 21,701 once invoked, about $0.0002 per session on Opus 5.5. 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.
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…
Reviewer
Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.