Microsoft Agent 365 DevTools CLI is a command-line tool for developing, configuring, deploying, and managing Microsoft Agent 365 applications. Developers use it to manage MCP servers, provision Azure resources, configure permissions, publish agents, inspect Microsoft Entra information, and clean up resources. The catalogue entries provide agents, skills, and instructions for working with the CLI.
Borrowing it
Nothing to install: this file belongs to microsoft/Agent365-devTools. 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-devTools/main/.claude/skills/review-staged/SKILL.mdgit clone --depth 1 https://github.com/microsoft/Agent365-devToolsWrote 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/skills/microsoft/agent365-devtools/review-staged)<a href="https://agentmods.dev/skills/microsoft/agent365-devtools/review-staged"><img src="https://agentmods.dev/badge/skills/microsoft/agent365-devtools/review-staged/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/skills/microsoft/agent365-devtools/review-staged"><img src="https://agentmods.dev/badge/skills/microsoft/agent365-devtools/review-staged.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00032 | $0.06526 |
| Opus 5.5 | $0.00013 | $0.02610 |
| Sonnet 5.5 | $0.00006 | $0.01305 |
| Haiku 4.5 | $0.00003 | $0.00653 |
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 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.
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 — 268 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review Staged Files Skill
Generate AI-powered code review comments covering both your currently staged changes and all commits on the branch since it diverged from main. This gives the same full-branch view that Copilot and other PR reviewers see — not just what you're about to commit.
Usage
/review-staged # Review staged changes + full branch diff against main
/review-staged --verbose # Show detailed analysis
Examples:
/review-staged- Review staged changes and all branch commits not yet on main/review-staged --verbose- Show detailed analysis with full context
What this skill does
- Checks for staged files using
git diff --staged --name-only - Fetches staged changes using
git diff --staged - Fetches full branch diff using
git diff $(git merge-base HEAD origin/main)...HEAD— covers all commits on the branch, not just staged files. This prevents issues in prior commits from going unreviewed. - Combines both diffs for review: staged diff = what you're about to add; branch diff = full PR picture that Copilot will see
- Performs architectural review: Questions design decisions, checks for scope creep, validates use cases
- Analyzes changes for security, testing, design patterns, and code quality issues
- Differentiates contexts: CLI code vs GitHub Actions code (different standards)
- Creates actionable feedback: Specific refactoring suggestions based on file names and patterns
- Verifies documentation completeness — detects user-visible surface changes (new CLI flags, renamed public types, payload contract changes, etc.) and verifies
CHANGELOG.md+ relevantREADME.md/design.mdare updated in the same diff. For renames, greps all*.mdfiles for stale references. See the Documentation Completeness section in.claude/agents/pr-code-reviewer.mdfor detection rules and severity calibration. - Runs the test suite and measures per-test timing — flags any test taking > 1 second as a performance regression
- Generates structured review document saved to a markdown file
- Shows summary of all issues found organized by severity
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 268 lines · 32 tokens per session scan A a00203ca73ad
review-staged is a skill published in the GitHub repository microsoft/Agent365-devTools (61 stars, last pushed yesterday), licensed MIT. It adds 32 tokens to every session and 6,526 once invoked, about $0.0001 per session on Opus 5.5. 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 skills, from other repositories
review-implement-phase
Implements triaged review actions, commits focused fixes, and posts Done plus resolves threads. Use when the user wants only the implementation phase of the review-framework workflow.
pr
Draft a PR body from OMC's paper trail — the smallest visual that proves the change, evidence consumed from the verify protocol (never re-collected), reversibility from the ADR test on the diff, glossary language throughout.
otto-pr-review-loop
Run Polly and OCR on a PR until all findings settle.
engram-branch-pr
PR creation workflow for Engram following the issue-first enforcement system. Trigger: When creating a pull request, opening a PR, or preparing changes for review.
verify-behavior
Verify or reproduce visible product behavior by driving the real UI with pi-computer-use's checked tools, requiring verified expect postconditions and durable state evidence for meaningful UI flows. Use when triage needs visual reproduction, implementation needs behavioral proof, review needs interactive confirmation…
github-contributor
A step-by-step guide for contributing code, tests, documentation, or build changes to open-source projects you do not maintain. It explains how to prepare a pull request that follows the project’s rules and is easier for maintainers to review.