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 skills/microsoft/agent365-devtools/review-stagednpx skills add microsoft/Agent365-devTools --skill review-stagedgit clone --depth 1 https://github.com/microsoft/Agent365-devToolsWhat 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.00032 | $0.06526 |
| Opus 5 | $0.00016 | $0.03263 |
| Sonnet 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 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 — 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.
- 2d 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 5d ago), licensed MIT. It adds 32 tokens to every session and 6,526 once invoked, about $0.0002 per session on Opus 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.