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 scaffold-test-filesgit 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/scaffold-test-files)<a href="https://agentmods.dev/skills/hyeonu-cha/dotnet-coverage-mcp/scaffold-test-files"><img src="https://agentmods.dev/badge/skills/hyeonu-cha/dotnet-coverage-mcp/scaffold-test-files/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/scaffold-test-files"><img src="https://agentmods.dev/badge/skills/hyeonu-cha/dotnet-coverage-mcp/scaffold-test-files.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.00106 | $0.01468 |
| Opus 5 | $0.00053 | $0.00734 |
| Sonnet 5 | $0.00021 | $0.00294 |
| Haiku 4.5 | $0.00011 | $0.00147 |
Grade A, and why
scaffold-test-files 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 10d 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 — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scaffold Test Files
Given a .NET source file, automatically create matching unit test and integration test directories and files under the test project, following the project's existing conventions and clean DI patterns.
When to Use
- User selects a source file and wants test files created for it
- User asks to "set up tests for this file" or "create test structure for X"
- Starting a new coverage session where no test file exists yet
- Adding integration test support alongside existing unit tests
When Not to Use
- Test files already exist for the source file — use
improve-test-coverageinstead - User only wants to run existing tests — use
run-coverage - User wants to inspect coverage gaps — use
analyze-coverage-gaps - Non-.NET project
Inputs
| Input | Required | Description |
|---|---|---|
sourceFilePath |
Yes | Full path to the .cs source file to create tests for |
testTypes |
No | Comma-separated list: unit, integration, or both (default: both) |
Workflow
Step 1: Analyze source file
Read the source file to extract:
- Namespace (e.g.,
MainProject.Subproject.Services) - Class name (e.g.,
ExampleService) - Constructor parameters — all injected interfaces (e.g.,
IRepository,ILogger<T>) - Public methods — names and signatures to create test stubs for
Step 2: Detect test project structure
Scan the solution for test projects:
glob **/*Test*.csproj
glob **/*Tests*.csproj
Determine the layout:
- Separate projects:
UnitTests.csprojandIntegrationTests.csprojexist separately → use each - Single project: One test
.csprojwith folders likeUnit/andIntegration/inside → use subfolders - No test project: Inform the user they need to create one first
Step 3: Mirror directory structure
Map the source path to test paths by mirroring the subfolder structure:
Source: MainProject/Subproject/Services/ExampleService.cs
Separate projects:
TestProject.UnitTests/Subproject/Services/ExampleServiceTests.csTestProject.IntegrationTests/Subproject/Services/ExampleServiceIntegrationTests.cs
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago First seen · 129 lines · 106 tokens per session scan A cd22b128d641
scaffold-test-files is a skill published in the GitHub repository Hyeonu-Cha/dotnet-coverage-mcp (1 stars, last pushed 4d ago), licensed MIT. It adds 106 tokens to every session and 1,468 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
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…
csharp-dotnet
Use when writing, reviewing, testing, or shipping C# / .NET code — ASP.NET Core APIs (minimal APIs vs controllers), EF Core data access, async correctness, solution layout in .cs/.csproj/.sln. NOT a Java/Spring backend (that is spring-boot), NOT a Node/TypeScript backend (that is nestjs), NOT framework-neutral REST…