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 skills add Hyeonu-Cha/dotnet-coverage-mcp --skill improve-test-coveragegit 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/skills/hyeonu-cha/dotnet-coverage-mcp/improve-test-coverage)<a href="https://agentmods.dev/skills/hyeonu-cha/dotnet-coverage-mcp/improve-test-coverage"><img src="https://agentmods.dev/badge/skills/hyeonu-cha/dotnet-coverage-mcp/improve-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/skills/hyeonu-cha/dotnet-coverage-mcp/improve-test-coverage"><img src="https://agentmods.dev/badge/skills/hyeonu-cha/dotnet-coverage-mcp/improve-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.00139 | $0.02084 |
| Opus 5 | $0.00069 | $0.01042 |
| Sonnet 5 | $0.00028 | $0.00417 |
| Haiku 4.5 | $0.00014 | $0.00208 |
Grade A, and why
improve-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 9d 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 — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Improve Test Coverage Iteratively
Autonomously run tests, identify coverage gaps, write targeted unit tests, and repeat until both line and branch coverage reach 80% or no further improvement is possible.
When to Use
- User asks to "improve coverage", "get to 80% coverage", or "write tests for X"
- Starting an automated coverage improvement session for a class or project
- Coverage is below 80% and the user wants tests written automatically
When Not to Use
- User only wants a coverage report without writing tests — use
run-coverage - User wants to inspect a specific method's branches only — use
analyze-coverage-gaps - Project has no existing test file to append to (create one first)
Inputs
| Input | Required | Description |
|---|---|---|
sourcePath |
Yes | Scope target: a .cs file, a folder, or a .csproj project |
testProjectPath |
Yes | Full path to the .csproj test project |
filter |
Yes | Test filter string — use * or broad filter for batch/folder/project scope |
lineBudget |
No | Max total lines per batch (default: 300). Small files get grouped, large files run solo |
workingDir |
No | Working directory; defaults to project directory |
includeClass |
No | Do NOT pass this in the iterative workflow. It scopes coverage to a single class and would skew batch-level numbers. Only used by run-coverage for single-class reports. |
Workflow
Step 0: Setup and discover scope
- Verify
reportgeneratoris installed (dotnet tool list -g); install if missing - Call
GetSourceFileswithsourcePathandlineBudgetto get:batches— files grouped by line budget (small files together, large files solo), each file carrying itslinesandmethodCountmetadatabatchCount— how many cycles to expect
Example response:
{
"scope": "folder",
"totalFiles": 18,
"totalLines": 4200,
"lineBudget": 300,
"batchCount": 8,
"batches": [
[{"path": "SmallA.cs", "lines": 80}, {"path": "SmallB.cs", "lines": 120}, {"path": "SmallC.cs", "lines": 90}],
[{"path": "BigService.cs", "lines": 920}]
]
}
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.
- 9d ago First seen · 156 lines · 139 tokens per session scan A 06102412ab76
improve-test-coverage is a skill published in the GitHub repository Hyeonu-Cha/dotnet-coverage-mcp (1 stars, last pushed 2d ago), licensed MIT. It adds 139 tokens to every session and 2,084 once invoked, about $0.0007 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-31.
Other skills, from other repositories
maintain-discatsharp
Review, modify, test, document, or release the DisCatSharp repository. Use for DisCatSharp source changes, API additions and migrations, Discord payload models, serialization, command synchronization, Gateway dispatch, REST behavior, analyzer work, multi-target testing, DocFX generation, release notes, and repository…
author-test
Generate a test given sample. Parameters: C# SDK repository root; Package name: one of Azure.AI.Projects, Azure.AI.Projects.Agents or Azure.AI.Extensions.OpenAI; the sample to use as a starting point for the test.
migrate-mstest-v3-to-v4
Use this skill before answering, planning, or editing any MSTest 3.x-to-4.x upgrade or post-upgrade failure. Triggers include "MSTest v4 breaking changes"; CS0507/CS0103/CS1061/CS1615; ExecuteAsync, CallerInfo, DisplayName, or custom TestMethodAttribute; ClassCleanupBehavior; ContainsKey; ThrowsExactly or…
migrate-xunit-to-mstest
Convert .NET tests from xUnit.net v2/v3 to MSTest v4 while preserving VSTest or MTP. Use for replacing xunit packages, Fact/Theory/InlineData/MemberData, assertions, IClassFixture/ICollectionFixture, ITestOutputHelper, TestContext cancellation, traits/Owner, skips, timeouts, and xUnit parallelization. Also use when a…
migrate-xunit-to-xunit-v3
Migrate .NET test projects from xUnit.net v2 to xunit.v3 and fix v3 breaks. Use for package/CPM conversion, OutputType=Exe, preserving the VSTest or MTP runner (including projects currently using YTest.MTP.XUnit2), incompatible TFMs, async void tests, string-to-Type attributes, custom Fact/Theory/BeforeAfterTest…
archunitnet
Use the open-source free ArchUnitNET library for architecture rules in .NET tests. Use when a repo needs richer architecture assertions than lightweight fluent rule libraries usually provide. USE FOR: the repo uses or wants ArchUnitNET; architecture testing needs richer modeling than simple dependency checks. DO NOT…