microsoft/Agent365-nodejs is a Node.js and TypeScript SDK for building Microsoft 365 agents with observability, notifications, runtime utilities, and development tools. Developers use it for agents connected to platforms such as Microsoft 365, Teams, Copilot Studio, and Webchat, while the catalogue entries are agents and instructions for the SDK.
Borrowing it
Nothing to install: this file belongs to microsoft/Agent365-nodejs. 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-nodejs/main/.claude/agents/test-coverage-reviewer.mdgit clone --depth 1 https://github.com/microsoft/Agent365-nodejsWrote 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-nodejs/test-coverage-reviewer)<a href="https://agentmods.dev/agents/microsoft/agent365-nodejs/test-coverage-reviewer"><img src="https://agentmods.dev/badge/agents/microsoft/agent365-nodejs/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-nodejs/test-coverage-reviewer"><img src="https://agentmods.dev/badge/agents/microsoft/agent365-nodejs/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.00000 | $0.02296 |
| Opus 5.5 | $0.00000 | $0.00918 |
| Sonnet 5.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 2mo 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 — 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.
- 2mo ago 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 today), 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
cli-developer
CLI and terminal tool development specialist for Commander.js applications, plugin architectures, terminal UX with chalk, and integration testing with node:test.
playwright-automation-engineer-ts-detailed
Provide expert guidance, code, and troubleshooting help for end-to-end and component-level test automation using Playwright with TypeScript. Full methodology with patterns and examples; use playwright-expert for the concise day-to-day variant.
hcc-frontend-iqe-to-playwright-converter
Use this agent to convert IQE/Selenium tests to Playwright TypeScript. This agent implements proper Red Hat SSO authentication (global or isolated), converts fixtures and page objects, modernizes selectors and wait patterns, uses symbolic timeout constants, handles parametrized tests, and organizes converted files by…
testing-engineer
Testing specialist for Rust, TypeScript, and Luau/Lua projects focused on comprehensive test coverage, test infrastructure, and quality assurance. Applies the project's language rules from the stack profile. Use PROACTIVELY when adding new functionality that requires tests, investigating test failures, or setting up…
typescript-pro
Master TypeScript with advanced types, generics, and strict type safety. Handles complex type systems, decorators, and enterprise-grade patterns. Use PROACTIVELY for TypeScript architecture, type inference optimization, or advanced typing patterns.
test-generator
Use this agent to generate high-quality TypeScript unit tests for a target file or directory. Detects the host project's test runner (Jest, Vitest, node:test) and follows the project's documented testing standards.