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 managedcode/dotnet-skills --skill coverletgit clone --depth 1 https://github.com/managedcode/dotnet-skillsWrote 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/managedcode/dotnet-skills/coverlet)<a href="https://agentmods.dev/skills/managedcode/dotnet-skills/coverlet"><img src="https://agentmods.dev/badge/skills/managedcode/dotnet-skills/coverlet.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00114 | $0.01167 |
| Opus 5 | $0.00057 | $0.00583 |
| Sonnet 5 | $0.00023 | $0.00233 |
| Haiku 4.5 | $0.00011 | $0.00117 |
Grade A, and why
coverlet 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 4d 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Coverlet for .NET
Trigger On
- the repo uses or wants
coverlet - CI needs line or branch coverage for .NET tests
- the team needs to choose between
coverlet.collector,coverlet.msbuild, orcoverlet.console
Value
- produce a concrete project delta: code, docs, config, tests, CI, or review artifact
- reduce ambiguity through explicit planning, verification, and final validation skills
- leave reusable project context so future tasks are faster and safer
Do Not Use For
- coverage report rendering by itself
- repos that intentionally use a different coverage engine
Inputs
- the nearest
AGENTS.md - active runner model: VSTest or Microsoft.Testing.Platform
- target test projects
Quick Start
- Read the nearest
AGENTS.mdand confirm scope and constraints. - Run this skill's
Workflowthrough theRalph Loopuntil outcomes are acceptable. - Return the
Required Result Formatwith concrete artifacts and verification evidence.
Workflow
- Choose the driver deliberately:
coverlet.collectorfor VSTestdotnet test --collectcoverlet.msbuildfor MSBuild property-driven runscoverlet.consolefor standalone scenarios
- Add coverage packages only to test projects.
- Do not mix
coverlet.collectorandcoverlet.msbuildin the same test project. - Pair raw coverage collection with
ReportGeneratoronly when humans need rendered reports.
Bootstrap When Missing
If coverage is not configured yet:
- Detect current state:
rg -n "coverlet\\.(collector|msbuild)|CollectCoverage|XPlat Code Coverage" -g '*.csproj' -g '*.props' -g '*.targets' .dotnet tool list --localdotnet tool list --globalcommand -v coverlet
- Install exactly one driver path:
- VSTest collector:
dotnet add TEST_PROJECT.csproj package coverlet.collector - MSBuild driver:
dotnet add TEST_PROJECT.csproj package coverlet.msbuild - Console tool:
dotnet new tool-manifest(if missing) anddotnet tool install coverlet.console
- VSTest collector:
- Record one concrete local and CI command in
AGENTS.md:- collector:
dotnet test TEST_PROJECT.csproj --collect:"XPlat Code Coverage" - msbuild:
dotnet test TEST_PROJECT.csproj /p:CollectCoverage=true /p:CoverletOutputFormat=cobertura - console:
dotnet tool run coverlet TEST_ASSEMBLY.dll --target "dotnet" --targetargs "test TEST_PROJECT.csproj --no-build"
- collector:
- Run the chosen command once and return
status: configuredorstatus: improved. - If another coverage engine already owns coverage for this repo, return
status: not_applicable.
What ships with it
4 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.
- 4d ago First seen · 115 lines · 114 tokens per session scan A fdb5e40f553f
coverlet is a skill published in the GitHub repository managedcode/dotnet-skills (477 stars, last pushed 2d ago), licensed MIT. It adds 114 tokens to every session and 1,167 once invoked, about $0.0006 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-09-03.
Other skills, from other repositories
rust-development
Idiomatisk Rust-utvikling med cargo, clippy, error handling, async/tokio, unsafe og testing.
infra-test
Run the full IaC test suite — Bicep linting, ARM TTK (if applicable), Terraform validate, Pester unit and integration tests. Use before deploying or after making infrastructure changes.
test-sweep
Run all test suites (unit, integration, API, E2E) and aggregate results into a summary report. Use after completing execution slices or before the Review Gate.
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.
winui-ui-testing
Automated UI testing for Windows desktop apps — generate a batch test script with the winapp ui UI Automation harness, run all tests in one pass, read results. Covers element assertions, interactions, value checking (TextBox, ComboBox, ToggleSwitch), keyboard shortcuts and typing (send-keys), hover, drag-and-drop…
testing-strategies
Comprehensive testing strategy covering unit, integration, e2e, property-based, and mutation testing with practical patterns.