A tool workflow that creates a self-contained HTML report from a .NET project's test map. The report shows features, scenarios, step bindings, classes, endpoints, and optionally project dependencies.

Use it to make an HTML overview or drill-down of a .NET test suite, including its scenarios and dependency graph.

It turns a test suite's internal map into a file that people can open and inspect in a browser. It also checks that the required map exists and is up to date before reporting.

report — Skill for Claude Code by Karzone/TestAtlas

Install

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.

Any agent

npx skills add Karzone/TestAtlas --skill report

Clone the repo

git clone --depth 1 https://github.com/Karzone/TestAtlas

Made for: Claude Code.

Or install testatlas, the plugin that ships this one along with the rest of its 3 skills, 1 hook, 1 MCP server.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/karzone/testatlas/report/github.svg)](https://agentmods.dev/skills/karzone/testatlas/report)

Your own site

<a href="https://agentmods.dev/skills/karzone/testatlas/report"><img src="https://agentmods.dev/badge/skills/karzone/testatlas/report/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/karzone/testatlas/report"><img src="https://agentmods.dev/badge/skills/karzone/testatlas/report.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 80 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 523 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00080	$0.00523
Opus 5.5	$0.00032	$0.00209
Sonnet 5.5	$0.00016	$0.00105
Haiku 4.5	$0.00008	$0.00052

Measured 13d ago against content hash e0e750fa52de, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

report 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 13d 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.

claude-plugin/skills/report/SKILL.md · 46 lines

What it actually says

Write the TestAtlas report

The report is one self-contained HTML file written from the map (codemap.db) by the testatlas command-line tool. It is not an MCP tool: run it in the shell. Nothing is uploaded and nothing but the HTML file is written.

Check the tools are there: command -v testatlas testatlas-mcp (PowerShell: Get-Command testatlas, testatlas-mcp). If either is missing, offer these first and run them when the person agrees (they need the .NET 8 SDK or later and reach only nuget.org):
```
dotnet tool install --global TestAtlas.Cli
```
```
dotnet tool install --global TestAtlas.Mcp
```
Make sure there is a map to report on. If there is no codemap.db at the project root, or the session-start note said the map is stale, or .cs / .feature files have changed since it was built, build it first with /testatlas:index. Never run the report against a missing map.
From the project root run:
```
testatlas report codemap.db --html codemap.html
```
Exit code 0 is a clean run and 1 is a run that completed with warnings; in both the file was written. Relay any warnings. 2 is a failure: show the message.
If the person asked for the dependency graph or the project map, or for "everything", also run:
```
testatlas map codemap.db --html codemap-map.html
```
Say where each file was written, as a full path, and offer to open it in the browser. Do not open it unasked. To write somewhere else, pass another path to --html.

Do not commit the HTML files unless the repository already tracks them; like codemap.db they are build artefacts and go stale with the next change.

Changes

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.

13d ago First seen · 46 lines · 80 tokens per session scan A e0e750fa52de

Subscribe to this mod's changes

report is a skill published in the GitHub repository Karzone/TestAtlas (3 stars, last pushed 6d ago), licensed MIT. It adds 80 tokens to every session and 523 once invoked, about $0.0003 per session on Opus 5.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-10-04.

C# and .NET Documents Testing ai-agents bdd code-analysis dependency-graph developer-tools

foundry-hosted-agent-validation

Step-by-step process for validating a Python Foundry hosted agent sample (under python/samples/04-hosting/foundry-hosted-agents/) end to end — running it locally (native runtime and azd ai agent run) and after deploying it to an Azure AI Foundry project with azd. Use this when asked to validate a hosted agent sample.

microsoft/agent-framework · 82 tokens

build-and-test

How to build and test .NET projects in the Agent Framework repository. Use this when verifying or testing changes.

microsoft/agent-framework · 26 tokens

verify-dotnet-samples

How to build, run and verify the .NET sample projects in the Agent Framework repository. Use this when a user wants to verify that the samples still function as expected.

microsoft/agent-framework · 40 tokens

typescript-providers

Implement, modify, test, or document TypeScript provider packages under ts/packages/providers, including framework adapters for OpenAI, Anthropic, Google, LangChain, Mastra, Vercel, LlamaIndex, Cloudflare, Claude Agent SDK, and TypeSafe. Use for provider-specific TS work; do not use for core-only changes.

ComposioHQ/composio · 73 tokens

ci

Configure Ginkgo for continuous integration — the recommended CLI flag set and the rationale for each flag (-r -p --randomize-all --randomize-suites --fail-on-pending --fail-on-empty --keep-going --cover --race --trace --json-report --timeout --poll-progress-after/-interval), invoking via go run to pin the CLI to…

onsi/ginkgo · 151 tokens

setup

Wire Ginkgo into a Go package — install the ginkgo CLI and Ginkgo+Gomega, ginkgo bootstrap to generate the suitetest.go (TestXxx/RegisterFailHandler(Fail)/RunSpecs), the package xxxtest convention, dot-import alternatives (aliased import, dsl/ subpackages, --nodot), ginkgo generate, and testing.T interop via…

onsi/ginkgo · 118 tokens