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/post-review-commentsgit 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.04623 |
| Opus 5 | $0.00000 | $0.02312 |
| Sonnet 5 | $0.00000 | $0.00925 |
| Haiku 4.5 | $0.00000 | $0.00462 |
Grade B, and why
post-review-comments scanned grade B with 1 finding 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
sudo apt update && sudo apt upgrade gh -y How it starts
The opening of the file, as written. The whole thing — 574 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Post Review Comments to GitHub
Post code review findings from a review file (generated by /review-pr or /review-staged) as comments on the associated GitHub pull request.
Usage
/post-review-comments [REVIEW_FILE_PATH]
Arguments:
REVIEW_FILE_PATH(optional) - Path to the review file. If omitted, uses the most recent review file in.codereviews/.
Examples:
/post-review-comments- Post comments from the most recent review/post-review-comments .codereviews/claude-pr187-20260124_120000.md- Post from specific review file
Instructions
You are posting code review findings to GitHub as PR comments. Findings with exact line information will be posted as inline comments directly on the code. Findings without line info will be posted as regular PR comments.
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 2>/dev/null | head -1On Windows, use PowerShell:
(Get-ChildItem .codereviews/claude-*.md | Sort-Object LastWriteTime -Descending | Select-Object -First 1).FullName -
Read the review file completely
-
Validate the review file:
- Must contain "PR Number:" in the metadata section
- If "PR Number:" is not found or is empty, inform the user this skill only works with PR reviews (not staged reviews) and exit
-
Extract key information:
- PR Number: Extract from the
PR Number:field (e.g.,#187→187) - PR Title: Extract from
PR Title:field - Approval Status: Extract from
Final Status:field - HEAD Commit: Extract from
HEAD Commit:field (required for inline comments)
- PR Number: Extract from the
Step 2: Parse Findings
Parse ALL findings from the review file. Findings are formatted as:
#### [CRM-XXX] Issue Title
| Field | Value |
|-------|-------|
| **Identified By** | `agent-name` |
| **File** | `path/to/file.ext` |
| **Line(s)** | 42-58 |
| **Diff Line** | 47 |
| **Diff Side** | RIGHT |
| **Severity** | `medium` |
...
**Description:**
<description text>
**Diff Context:**
<code block>
**Suggestion:**
<suggestion text>
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 · 574 lines · 0 tokens per session scan B 1ef75985cb41
post-review-comments 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 4,623 tokens. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.