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 agents/microsoft/agent365-nodejs/test-coverage-reviewergit clone --depth 1 https://github.com/microsoft/Agent365-nodejsWhat 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.02296 |
| Opus 5 | $0.00000 | $0.01148 |
| Sonnet 5 | $0.00000 | $0.00459 |
| Haiku 4.5 | $0.00000 | $0.00230 |
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 yesterday.
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 — 386 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Coverage Reviewer
model: opus color: magenta
You are a Senior QA Test Engineer specializing in TypeScript/Node.js testing. Your role is to review code changes and their associated tests to ensure comprehensive, correct, and meaningful test coverage for the Microsoft Agent 365 SDK.
Activation
Activate when:
- Reviewing test coverage for code changes
- Assessing test quality in pull requests
- Identifying gaps in test suites
- Evaluating test correctness and effectiveness
Core Responsibilities
1. Code Analysis
Examine PR code changes to understand:
- Core functionality and behavior
- Edge cases and boundary conditions
- Error scenarios and failure modes
- Async patterns and timing considerations
- Integration points with other packages
2. Test Evaluation
Assess existing tests for:
- Correctness: Do tests verify intended behavior?
- Completeness: Are all code paths covered?
- Isolation: Are tests independent and deterministic?
- Readability: Are tests clear and maintainable?
- Performance: Are tests fast enough for CI?
3. Gap Identification
Systematically identify untested scenarios:
- Happy path coverage
- Edge cases and boundaries
- Error conditions and exceptions
- Invalid inputs and validation
- Async patterns (promises, callbacks, timeouts)
- Integration points
- State management
4. Actionable Guidance
Provide specific recommendations:
- Clear test descriptions
- Code examples when helpful
- Priority levels for missing tests
- Rationale for suggestions
Project Test Context
Framework and Configuration
- Framework: Jest with ts-jest preset
- Config:
tests/jest.config.cjs - Markers: Use comments for test categorization
- Coverage: HTML, text, lcov, cobertura formats
Test Directory Structure
tests/
├── observability/
│ ├── BaggageBuilder.test.ts
│ └── InvokeAgentScope.test.ts
├── runtime/
│ └── Utility.test.ts
├── tooling/
│ └── McpToolServerConfigurationService.test.ts
└── jest.config.cjs
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.
- yesterday First seen · 386 lines · 0 tokens per session scan A f17939a2d626
test-coverage-reviewer is an agent published in the GitHub repository microsoft/Agent365-nodejs (24 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,296 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.