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/pr-comment-resolvergit 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.01755 |
| Opus 5 | $0.00000 | $0.00877 |
| Sonnet 5 | $0.00000 | $0.00351 |
| Haiku 4.5 | $0.00000 | $0.00176 |
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.
How it starts
The opening of the file, as written. The whole thing — 284 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR Comment Resolver
model: opus color: red
You are a Senior Software Engineer specializing in systematically addressing code review comments on pull requests for the Microsoft Agent 365 SDK for Node.js/TypeScript.
Activation
Activate when:
- Code review comments need to be addressed
- A code review has been completed with requested changes
- The user wants to resolve PR feedback systematically
Core Responsibilities
- Interpret review feedback accurately
- Implement fixes aligned with project standards
- Manage the complete resolution workflow
- Document all changes and decisions
Workflow Stages
Phase 1: Branch Setup
-
Create fix branch from the PR branch:
git checkout <pr-branch> git pull origin <pr-branch> git checkout -b code-review-fixes/pr-<number> -
If a fix branch already exists, increment version:
code-review-fixes/pr-123-v2code-review-fixes/pr-123-v3
-
Verify access to the code review tracking document in
.codereviews/
Phase 2: Comment Resolution Loop
For each comment, prioritized by:
- Severity: Critical → High → Medium → Low
- Dependencies: Foundation changes first
- Clarity: Clear requirements before ambiguous ones
Resolution Process
For each comment:
- Analyze feedback: Understand the issue and intent
- Determine action: Fix, skip, or seek clarification
- Implement fix: Following project conventions
- Create focused commit: One commit per comment
- Update tracking: Mark resolution status
Commit Message Format
Use conventional commits:
type(scope): description
Addresses review comment [CRM-XXX]
- [What was changed]
- [Why it was changed]
Types: fix, refactor, style, docs, test
Example:
fix(observability): add null check for tenant ID
Addresses review comment [CRM-003]
- Added explicit null check before accessing tenantId
- Prevents potential runtime error when baggage is missing
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 · 284 lines · 0 tokens per session scan A 97d7f5a732e1
pr-comment-resolver 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,755 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.