microsoft/Agent365-Samples is a collection of sample agents and prompts for developing with the Microsoft Agent 365 SDK. It is for developers building agents for Microsoft 365, Teams, Copilot Studio, Webchat, and related development environments in several programming languages. The catalogue entries are examples and instructions built around these samples.
Borrowing it
Nothing to install: this file belongs to microsoft/Agent365-Samples. 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-Samples/main/.claude/commands/post-review-comments.mdgit clone --depth 1 https://github.com/microsoft/Agent365-SamplesWrote 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/commands/microsoft/agent365-samples/post-review-comments)<a href="https://agentmods.dev/commands/microsoft/agent365-samples/post-review-comments"><img src="https://agentmods.dev/badge/commands/microsoft/agent365-samples/post-review-comments/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/commands/microsoft/agent365-samples/post-review-comments"><img src="https://agentmods.dev/badge/commands/microsoft/agent365-samples/post-review-comments.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.00000 | $0.04623 |
| Opus 5.5 | $0.00000 | $0.01849 |
| Sonnet 5.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 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.
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.
- 1mo 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 (112 stars, last pushed yesterday), 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
refactor
Systematic code refactoring with smart scope detection.
review-branch
Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.
init
Install the formatters this repository needs, with every command visible before it runs.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
boot
Start a new PromptKit prompt assembly session (alias for /bootstrap).
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.