Borrowing it
Nothing to install: this file belongs to managedcode/dotPilot. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/managedcode/dotPilot/main/.codex/skills/mcaf-dotnet-reportgenerator/SKILL.mdgit clone --depth 1 https://github.com/managedcode/dotPilotWrote 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/dotpilot/mcaf-dotnet-reportgenerator)<a href="https://agentmods.dev/skills/managedcode/dotpilot/mcaf-dotnet-reportgenerator"><img src="https://agentmods.dev/badge/skills/managedcode/dotpilot/mcaf-dotnet-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/dotpilot/mcaf-dotnet-reportgenerator"><img src="https://agentmods.dev/badge/skills/managedcode/dotpilot/mcaf-dotnet-reportgenerator.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.00052 | $0.00913 |
| Opus 5.5 | $0.00021 | $0.00365 |
| Sonnet 5.5 | $0.00010 | $0.00183 |
| Haiku 4.5 | $0.00005 | $0.00091 |
Grade A, and why
mcaf-dotnet-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 1mo 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.
This is a copy
91% identical to reportgenerator — 10 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MCAF: .NET ReportGenerator
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
1 file 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.
- 1mo ago First seen · 110 lines · 52 tokens per session scan A 6f627b36bd77
mcaf-dotnet-reportgenerator is a skill published in the GitHub repository managedcode/dotPilot (25 stars, last pushed 6mo ago), licensed MIT. It adds 52 tokens to every session and 913 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 91% identical to reportgenerator, differing in 10 lines, and is treated as a copy.
Other skills, from other repositories
scenario-design
Draft real-life test SCENARIOS (not smoke tests) from a change/feature spec. Derives edge-case, performance, frontend-quirk and error-handling scenarios with ISTQB techniques, routes each to a test level, and writes test-plan.md, emitting clarification questions on a spec gap. Use on "design test scenarios", "what…
Vizra ADK Evaluation Framework
Test and evaluate AI agents with automated evaluations, assertions, and LLM-as-a-Judge patterns.
run-dashboard-e2e-local-changes
Run Playwright E2E (tests/e2e/) against the docker/ all-in-one harness so it reflects LOCAL code changes, not a stale cached image.
goga-accept-test-assessment
Cell test coverage assessment for acceptance review.
goga-accept-usage-review
Validate cell-level usage files against actual implementation during acceptance.
goga-accept-scope
Defines the acceptance scope — the set of cells for a given functionality.