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-python/pr-comment-resolvergit clone --depth 1 https://github.com/microsoft/Agent365-pythonWhat 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.00385 | $0.02010 |
| Opus 5 | $0.00192 | $0.01005 |
| Sonnet 5 | $0.00077 | $0.00402 |
| Haiku 4.5 | $0.00038 | $0.00201 |
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 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.
This is a copy
91% identical to pr-comment-resolver — 23 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 — 145 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 - remove Kairo reference")
- 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.
- yesterday First seen · 145 lines · 385 tokens per session scan A 0e3f7581df2a
pr-comment-resolver is an agent published in the GitHub repository microsoft/Agent365-python (41 stars, last pushed 5d ago), licensed MIT. It adds 385 tokens to every session and 2,010 once invoked, about $0.0019 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to pr-comment-resolver, differing in 23 lines, and is treated as a copy.
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.