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 commands/microsoft/agent365-samples/resolve-reviewgit clone --depth 1 https://github.com/microsoft/Agent365-SamplesWhat 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.02043 |
| Opus 5 | $0.00000 | $0.01022 |
| Sonnet 5 | $0.00000 | $0.00409 |
| Haiku 4.5 | $0.00000 | $0.00204 |
Grade A, and why
resolve-review 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 2d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- resolve-review — 88% identical, 78 lines differ
How it starts
The opening of the file, as written. The whole thing — 234 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Resolve Review Comments
Automatically resolve code review comments that are marked as "Agent Resolvable: Yes" from a review generated by /review-pr or /review-staged.
Usage
/resolve-review [REVIEW_FILE_PATH]
Arguments:
REVIEW_FILE_PATH(optional) - Path to the review file. If omitted, uses the most recent review file in.codereviews/.
Examples:
/resolve-review- Resolve comments from the most recent review/resolve-review .codereviews/claude-pr123-20260124_143022.md- Resolve specific review
Instructions
You are resolving agent-resolvable code review comments. This skill supports two scenarios:
- PR Reviews: Changes are made in a git worktree to avoid disrupting your current work
- Staged Reviews: Changes are made directly in the current working directory after validation
Step 1: Locate and Parse the Review File
-
If
$ARGUMENTSis provided and non-empty, use that as the review file path -
Otherwise, find the most recent review file:
ls -t .codereviews/claude-*.md | head -1On Windows, use:
Get-ChildItem .codereviews/claude-*.md | Sort-Object LastWriteTime -Descending | Select-Object -First 1 -ExpandProperty FullName -
Read the review file and extract:
- Review type: PR review (contains "PR Number:") or staged review (contains "Review Type: Pre-commit")
- PR number (if PR review): Extract from the metadata
- All findings marked "Agent Resolvable: Yes": Parse the structured issues
-
If no resolvable issues are found, inform the user and exit.
-
Create a todo list tracking each resolvable issue to be fixed.
Step 2: Environment Setup (Branching Strategy)
For PR Reviews (use git worktree for isolation):
Git worktree allows you to work on a different branch without changing your current working directory. This is critical to avoid disrupting the user's in-progress work.
- Get the PR's head branch name:
gh pr view <PR_NUMBER> --json headRefName --jq '.headRefName'
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.
- 2d ago First seen · 234 lines · 0 tokens per session scan A e8c92493da0a
resolve-review is a command published in the GitHub repository microsoft/Agent365-Samples (106 stars, last pushed 29d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,043 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 commands, from other repositories
speckit.git.commit
Auto-commit changes after a Spec Kit command completes.
commit-all
Group all changes semantically and commit each group separately.
commit
Based on the above changes, create a single git commit.
commit
Safe git commit practices for MindRoom.
commit
智能生成 Git 提交信息并提交.
commit
Create a Conventional Commit with signoff.