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 run-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/run-coverage)<a href="https://agentmods.dev/skills/hyeonu-cha/dotnet-coverage-mcp/run-coverage"><img src="https://agentmods.dev/badge/skills/hyeonu-cha/dotnet-coverage-mcp/run-coverage.svg" alt="Measured on agentmods" 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.00100 | $0.01009 |
| Opus 5 | $0.00050 | $0.00504 |
| Sonnet 5 | $0.00020 | $0.00202 |
| Haiku 4.5 | $0.00010 | $0.00101 |
Grade A, and why
run-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 8d 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Run Tests with Coverage
Run a .NET test project with code coverage enabled and display a structured summary of line and branch coverage per class and method.
When to Use
- User wants to generate or refresh a coverage report
- User asks "what is the current coverage?" or "run the tests with coverage"
- Starting a new coverage improvement session to get a baseline
- Verifying coverage after manually writing tests
When Not to Use
- User wants to iteratively write tests to improve coverage — use
improve-test-coverage - User wants to find specific uncovered branches in a method — use
analyze-coverage-gaps - Project is not a .NET test project (no
.csproj, no NUnit/xUnit/MSTest references)
Inputs
| Input | Required | Description |
|---|---|---|
testProjectPath |
Yes | Full path to the .csproj test project file |
filter |
Yes | Test filter string matched against FullyQualifiedName (partial match if no dots; exact match if contains dots) |
workingDir |
No | Working directory; defaults to the project directory |
includeClass |
No | Restrict coverage collection to a single class name (e.g. OrderService), applied via coverlet's Include filter. Use ONLY when you want coverage scoped to one class. Do NOT pass a namespace — namespace-qualified names are not supported. Omit for broad/multi-class coverage. |
forceRestore |
No | Set to true after scaffolding a new test project or adding NuGet packages. |
sessionId |
No | Isolate output directories when multiple agents run concurrently. |
Workflow
Step 1: Verify prerequisites
Check that the reportgenerator global tool is installed:
dotnet tool list -g | grep reportgenerator
If missing, install it:
dotnet tool install -g dotnet-reportgenerator-globaltool
Step 2: Run tests with coverage
Call RunTestsWithCoverage with the provided testProjectPath and filter.
Pass includeClass only when coverage should be scoped to a single class (e.g. the specific class under test). Leave it unset for broad filters that span multiple classes — otherwise coverage numbers will be artificially zeroed for classes outside the include pattern.
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.
- 8d ago First seen · 91 lines · 100 tokens per session scan A 146d4ab67c2e
run-coverage is a skill published in the GitHub repository Hyeonu-Cha/dotnet-coverage-mcp (1 stars, last pushed yesterday), licensed MIT. It adds 100 tokens to every session and 1,009 once invoked, about $0.0005 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…