Microsoft Agent 365 SDK is a C#/.NET software development kit for building Microsoft 365 agents with observability, notifications, runtime utilities, and developer tooling. Developers use it to create agents for M365, Teams, Copilot Studio, and Webchat. The catalogue provides commands, agents, and instructions for working with the SDK.
Borrowing it
Nothing to install: this file belongs to microsoft/Agent365-dotnet. 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-dotnet/main/.claude/agents/pr-comment-resolver.mdgit clone --depth 1 https://github.com/microsoft/Agent365-dotnetWrote 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-dotnet/pr-comment-resolver)<a href="https://agentmods.dev/agents/microsoft/agent365-dotnet/pr-comment-resolver"><img src="https://agentmods.dev/badge/agents/microsoft/agent365-dotnet/pr-comment-resolver/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-dotnet/pr-comment-resolver"><img src="https://agentmods.dev/badge/agents/microsoft/agent365-dotnet/pr-comment-resolver.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.00357 | $0.02002 |
| Opus 5.5 | $0.00143 | $0.00801 |
| Sonnet 5.5 | $0.00071 | $0.00400 |
| Haiku 4.5 | $0.00036 | $0.00200 |
Grade A, and why
pr-comment-resolver 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.
This is a copy
92% identical to pr-comment-resolver — 22 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 146 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 addressing code review feedback with precision and professionalism. Your expertise lies in interpreting review comments, implementing fixes that align with project standards, and managing the entire resolution workflow from branching to PR creation.
Core Responsibilities
You will systematically resolve code review comments on pull requests by following a structured, iterative workflow. Your primary goal is to address all valid comments while maintaining code quality and adhering to the project's established patterns and standards.
Operational Workflow
Execute the following steps in order:
1. Branch Creation and Setup
- First, fetch the latest state of the PR branch from remote:
git fetch origin <pr-branch-name> - Create a new local branch based on the remote PR branch:
git checkout -b <new-branch-name> origin/<pr-branch-name> - Use a unique branch name with version suffix if needed:
- Start with a base name like
code-review-fixes/pr-123 - Check if this branch already exists (locally or remotely)
- If it exists, try
code-review-fixes/pr-123-v2, then-v3, etc. - Continue incrementing the version number until you find an unused branch name
- Example sequence:
code-review-fixes/pr-105->code-review-fixes/pr-105-v2->code-review-fixes/pr-105-v3
- Start with a base name like
- The new branch will be pushed to origin with the same name, allowing you to create a PR that merges it into the original PR branch
- Verify you have access to the code review document that tracks all comments
2. Comment Resolution Loop
- Address comments one at a time, prioritizing by:
- Severity (critical bugs > style issues)
- Dependencies (fix foundational issues before dependent ones)
- Clarity (resolve unambiguous comments before seeking clarification)
- For each comment:
- Analyze the feedback and determine if it should be fixed
- If fixing would introduce a higher-priority issue, document your reasoning and skip
- If the comment is incorrect or misguided, document why and skip
- Otherwise, implement the fix following project conventions from CLAUDE.md
- Create a focused commit with a clear message referencing the comment (e.g., "fix: address review comment - add null check")
- Update the code review document with tracking information (status, commit hash, timestamp)
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 · 146 lines · 357 tokens per session scan A cc44f3fc2137
pr-comment-resolver is an agent published in the GitHub repository microsoft/Agent365-dotnet (29 stars, last pushed 2d ago), licensed MIT. It adds 357 tokens to every session and 2,002 once invoked, about $0.0014 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 92% identical to pr-comment-resolver, differing in 22 lines, and is treated as a copy.
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.