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 reportgeneratorgit 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/reportgenerator)<a href="https://agentmods.dev/skills/managedcode/dotnet-skills/reportgenerator"><img src="https://agentmods.dev/badge/skills/managedcode/dotnet-skills/reportgenerator/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/managedcode/dotnet-skills/reportgenerator"><img src="https://agentmods.dev/badge/skills/managedcode/dotnet-skills/reportgenerator.svg" alt="Reviewed on agentmods" width="80" 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.00101 | $0.00986 |
| Opus 5 | $0.00051 | $0.00493 |
| Sonnet 5 | $0.00020 | $0.00197 |
| Haiku 4.5 | $0.00010 | $0.00099 |
Grade A, and why
reportgenerator 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 6d 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.
Copies of this mod
3 near-identical copies found in the catalogue:
- mcaf-dotnet-reportgenerator — 91% identical, 10 lines differ
- mcaf-dotnet-reportgenerator — 91% identical, 10 lines differ
- dotnet-reportgenerator — 91% identical, 12 lines differ
How it starts
The opening of the file, as written. The whole thing — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ReportGenerator for .NET
Trigger On
- the repo uses or wants
ReportGenerator - CI needs human-readable coverage reports
- multiple coverage files must be merged
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
- raw coverage collection with no reporting need
Inputs
- the nearest
AGENTS.md - existing coverage artifacts
- desired output formats
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
- Keep collection and rendering separate: Coverlet collects, ReportGenerator renders.
- Prefer the local or manifest-based .NET tool for reproducible CI runs.
- Choose output formats deliberately:
HtmlSummaryCoberturaMarkdownSummaryGithub- badges
- Merge multiple reports only when the repo really needs a consolidated view.
Bootstrap When Missing
If ReportGenerator is not configured yet:
- Detect current state:
rg --files -g '.config/dotnet-tools.json'dotnet tool list --localdotnet tool list --globalcommand -v reportgenerator
- Prefer local tool installation for reproducible CI:
dotnet new tool-manifest(if missing)dotnet tool install dotnet-reportgenerator-globaltool
- Add one explicit render command to
AGENTS.mdand CI, for example:dotnet tool run reportgenerator -reports:"**/coverage.cobertura.xml" -targetdir:"artifacts/coverage" -reporttypes:"HtmlSummary;Cobertura"
- Run the report command once and return
status: configuredorstatus: improved. - If raw coverage outputs are already sufficient and no rendered artifacts are needed, 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.
- 6d ago First seen · 112 lines · 101 tokens per session scan A a370d635af73
reportgenerator is a skill published in the GitHub repository managedcode/dotnet-skills (477 stars, last pushed 4d ago), licensed MIT. It adds 101 tokens to every session and 986 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-09-03.
Other skills, from other repositories
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…
rust-development
Idiomatisk Rust-utvikling med cargo, clippy, error handling, async/tokio, unsafe og testing.
playwright-testing
Generer og kjør Playwright E2E-tester for webapplikasjoner med page objects, auth fixtures og tilgjengelighetstester.
mutation-testing
Use when running mutation testing, killing mutants, verifying test quality, checking mutation score, or analyzing survivors after the test baseline is green.
generate-microcks-openapi-samples
Use when creating OpenAPI mock examples for Microcks, setting up request/response routing with dispatchers, or mapping request fields to mock responses.
outside-in-tdd
Use when writing tests from the outside-in, defining behavior before code, or any feature where tests should start from observable business behavior and let internal design emerge.