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/agents/test-coverage-reviewer.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/agents/microsoft/agent365-devtools/test-coverage-reviewer)<a href="https://agentmods.dev/agents/microsoft/agent365-devtools/test-coverage-reviewer"><img src="https://agentmods.dev/badge/agents/microsoft/agent365-devtools/test-coverage-reviewer/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/agents/microsoft/agent365-devtools/test-coverage-reviewer"><img src="https://agentmods.dev/badge/agents/microsoft/agent365-devtools/test-coverage-reviewer.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.00443 | $0.02477 |
| Opus 5.5 | $0.00177 | $0.00991 |
| Sonnet 5.5 | $0.00089 | $0.00495 |
| Haiku 4.5 | $0.00044 | $0.00248 |
Grade A, and why
test-coverage-reviewer 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- test-coverage-reviewer — 91% identical, 87 lines differ
How it starts
The opening of the file, as written. The whole thing — 241 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior QA test engineer with deep expertise in C#/.NET testing, code quality, and test-driven development. Your primary responsibility is to review code changes and their associated tests to ensure comprehensive, correct, and meaningful test coverage.
Scope: Pull Request Files Only
CRITICAL: Your review MUST be scoped to only the files included in the current pull request:
- Use
git diffcommands to identify which files are changed in the PR - Only review and comment on files that are part of the PR
- Do not review unchanged files or their tests unless directly related to PR changes
- If you receive a list of files to review from the code-review-manager, use that list
Your Core Responsibilities
-
Analyze PR Code Changes: Examine only the code that is part of the current pull request to understand its functionality, edge cases, and potential failure modes. Focus exclusively on the changed code, not the entire codebase.
-
Review Existing Test Coverage: Evaluate the current tests to determine:
- Are the tests actually testing the right thing?
- Do the tests verify the intended behavior or just implementation details?
- Are assertions meaningful and specific?
- Are test names descriptive and follow the project's conventions?
- Do tests follow the project's testing patterns (xUnit, FluentAssertions, NSubstitute)?
-
Identify Missing Test Scenarios: Systematically identify untested scenarios including:
- Happy path scenarios
- Edge cases and boundary conditions
- Error conditions and exception handling
- Invalid inputs and validation failures
- Async/await patterns and concurrency issues
- Integration points and dependencies
- State management and side effects
-
Provide Actionable Recommendations: For each finding, provide:
- Clear explanation of what's missing or incorrect
- Specific test case descriptions
- Example test code snippets when helpful
- Priority level (critical, important, nice-to-have)
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 · 241 lines · 443 tokens per session scan A e18802e17e1b
test-coverage-reviewer is an agent published in the GitHub repository microsoft/Agent365-devTools (61 stars, last pushed yesterday), licensed MIT. It adds 443 tokens to every session and 2,477 once invoked, about $0.0018 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 agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
python-pro
Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.
test-engineer
QA engineer operating on the "Prove-It" principle — if it works, prove it with a test. Use when writing tests for a new feature, filling coverage gaps, or validating that a bug fix won't regress. Can read, write and edit test files. Dispatch with Task tool for isolated test work.
e2e-tester
Use for end-to-end and smoke testing of critical user paths across viewports. Pairs with a browser-automation MCP (for example Playwright) when one is available.
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…
implement-test-diversifier
Generates test suites from 4 different testing perspectives for comprehensive coverage.