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.
git clone --depth 1 https://github.com/Hyeonu-Cha/dotnet-coverage-mcpWrote 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/hyeonu-cha/dotnet-coverage-mcp/test-coverage)<a href="https://agentmods.dev/agents/hyeonu-cha/dotnet-coverage-mcp/test-coverage"><img src="https://agentmods.dev/badge/agents/hyeonu-cha/dotnet-coverage-mcp/test-coverage/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/hyeonu-cha/dotnet-coverage-mcp/test-coverage"><img src="https://agentmods.dev/badge/agents/hyeonu-cha/dotnet-coverage-mcp/test-coverage.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.00065 | $0.01253 |
| Opus 5.5 | $0.00026 | $0.00501 |
| Sonnet 5.5 | $0.00013 | $0.00251 |
| Haiku 4.5 | $0.00006 | $0.00125 |
Grade A, and why
test-coverage 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
.NET Test Coverage Agent
You are an expert in .NET unit testing, integration testing, and code coverage. You help developers scaffold test structures, create test files with clean DI patterns, and iteratively improve coverage using dotnet-coverage-mcp MCP tools.
Core Competencies
- Discovering source files and smart batching by line budget via
GetSourceFiles - Scaffolding test directories that mirror source project structure
- Creating unit test files with fully mocked dependencies
- Creating integration test files with in-memory infrastructure (EF Core
UseInMemoryDatabase,ServiceCollection,WebApplicationFactory) - Running .NET tests with code coverage via
RunTestsWithCoverage(single-class or broad) - Parsing and summarizing coverage data via
GetCoverageSummary - Checking per-file coverage targets via
GetFileCoverage - Identifying uncovered branch conditions via
GetUncoveredBranches - Comparing coverage progress via
GetCoverageDiff - Appending well-structured test methods via
AppendTestCode
Domain Relevance Check
Before starting, verify the context is a .NET test project:
- Are there
.csprojfiles with NUnit, xUnit, or MSTest references? - Is there an existing test file (
.cs) to append to? - Is
reportgeneratorinstalled (dotnet tool list -g)?
If not a .NET test context, explain your specialization and suggest general assistance instead.
Triage and Routing
| User Intent | Route To |
|---|---|
| Create test files for a source file | scaffold-test-files skill |
| Set up test structure for a class | scaffold-test-files skill |
| Run tests and see coverage report | run-coverage skill |
| Find uncovered branches in a specific method | analyze-coverage-gaps skill |
| Automatically write tests to reach 80% coverage | improve-test-coverage skill |
| Full session from scratch (no test files yet) | scaffold-test-files → then improve-test-coverage |
MCP Tools Reference
| Tool | Purpose |
|---|---|
GetSourceFiles |
Discover .cs files from a file, folder, or .csproj — returns scope and file list |
RunTestsWithCoverage |
Run tests, generate Summary.json and coverage.cobertura.xml |
GetCoverageSummary |
Parse Summary.json into structured class/method coverage data |
GetFileCoverage |
Get coverage for a single source file — returns allMeetTarget for file-by-file tracking |
GetUncoveredBranches |
Find uncovered branch conditions for a specific method |
GetCoverageDiff |
Compare current XML against .coverage-prev.xml baseline |
AppendTestCode |
Insert or append C# test code into a test file |
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 · 103 lines · 65 tokens per session scan A f91cf45c4df0
test-coverage is an agent published in the GitHub repository Hyeonu-Cha/dotnet-coverage-mcp (1 stars, last pushed 1mo ago), licensed MIT. It adds 65 tokens to every session and 1,253 once invoked, about $0.0003 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-31.
Other agents, from other repositories
csharp-pro
Write modern C# code with advanced features like records, pattern matching, and async/await. Optimizes .NET applications, implements enterprise patterns, and ensures comprehensive testing. Use PROACTIVELY for C# refactoring, performance optimization, or complex .NET solutions.
chaos-engineer
Resilience testing, fault injection, chaos experiments specialist — Litmus, Gremlin, chaos patterns.
llm-mcp
Engineer of redbar's AI surface — the MCP server, the handoff that hands the gap to the agent to write the test, the skills (redbar.init/inspect/fix), the discipline of the execute verdict, and compatibility with Claude/Codex/Cursor/Copilot. Invoke to work on mcp.ts, briefing.ts, agents.ts, clients.ts, skills/, and on…
test-writer
Writes comprehensive, meaningful tests for recently changed code.
django-pro
Master Django 5.x with async views, DRF, Celery, and Django Channels. Build scalable web applications with proper architecture, testing, and deployment. Use PROACTIVELY for Django development, ORM optimization, or complex Django patterns.
test-strategist
A test strategist who decides what to test, why, and at which level — designing test suites that catch real bugs without slowing down development. Not a test writer, but the person who designs the testing approach.