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/review-stagedgit 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.01608 |
| Opus 5 | $0.00000 | $0.00804 |
| Sonnet 5 | $0.00000 | $0.00322 |
| Haiku 4.5 | $0.00000 | $0.00161 |
Grade A, and why
review-staged 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.
How it starts
The opening of the file, as written. The whole thing — 195 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review Staged Changes
Review staged (uncommitted) changes using a comprehensive multi-agent code review process. Use this before committing to get feedback on your changes.
Usage
/review-staged
No arguments required - reviews all currently staged changes.
Instructions
You are coordinating a comprehensive code review for staged changes that haven't been committed yet.
Step 1: Gather Staged Changes Information
First, collect information about the staged changes:
-
Get list of staged files:
git diff --cached --name-only -
Get the full diff of staged changes:
git diff --cached -
IMPORTANT: Save the diff output - you will need it to include relevant diff context snippets in each finding.
-
If there are no staged changes, inform the user and suggest they stage files with
git add. -
Create the
.codereviews/directory if it doesn't exist.
Step 2: Launch Parallel Code Reviews
Launch FOUR sub-agents in parallel using the Task tool. Each agent MUST receive:
- The list of staged files (so they stay scoped)
- The diff content for context
CRITICAL: You MUST launch all four agents in a SINGLE message with FOUR parallel Task tool calls:
-
security-compliance-reviewer (
subagent_type: security-compliance-reviewer)- Prompt: "Review staged changes for security compliance. Files changed: [list files]. This is a pre-commit review, not a PR. Focus on authentication, secrets, token handling, logging security, and input validation. Output your review in the structured markdown format. Since this is not a PR, omit PR Link fields or mark them as N/A."
-
agent365-anti-pattern-detector (
subagent_type: agent365-anti-pattern-detector)- Prompt: "Review staged changes for architectural anti-patterns. Files changed: [list files]. This is a pre-commit review, not a PR. Focus on initialization flow, message processing flow, observability patterns, and SDK usage. Output your review in the structured markdown format. Since this is not a PR, omit PR Link fields or mark them as N/A."
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 · 195 lines · 0 tokens per session scan A e7af749514ee
review-staged 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 1,608 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
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.
constitution
Create or update the project constitution from interactive or provided principle inputs.
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.