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 cwoodruff/dotnet-claude-workshop-content --skill gen-testsgit clone --depth 1 https://github.com/cwoodruff/dotnet-claude-workshop-contentWrote 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/cwoodruff/dotnet-claude-workshop-content/gen-tests)<a href="https://agentmods.dev/skills/cwoodruff/dotnet-claude-workshop-content/gen-tests"><img src="https://agentmods.dev/badge/skills/cwoodruff/dotnet-claude-workshop-content/gen-tests.svg" alt="Measured on agentmods" 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.00037 | $0.00338 |
| Opus 5 | $0.00018 | $0.00169 |
| Sonnet 5 | $0.00007 | $0.00068 |
| Haiku 4.5 | $0.00004 | $0.00034 |
Grade A, and why
gen-tests 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 8d 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
1 near-identical copy found in the catalogue:
- gen-tests — 100% identical, 0 lines differ
What it actually says
Generate xUnit Tests
Target: $ARGUMENTS
- Read the target and its dependencies before writing anything. Identify: public surface, branches, edge cases (null/empty, boundary values, cancellation, concurrency), and failure modes (not found, validation, exceptions).
- Enumerate the test cases first as a checklist in your response — happy paths, each failure path, each boundary — and note which are unit vs. integration.
- Write the tests:
- Naming:
MethodName_Scenario_ExpectedResult - Arrange / Act / Assert with blank-line separation
[Theory]+[InlineData]for parametric cases- Mock only at boundaries (repository interfaces, external clients); use real Core logic
- Inject
TimeProvider/ fakes rather than touching real time, filesystem, or network - Async tests return
Task, neverasync void
- Naming:
- Match existing test project conventions — fixture patterns, builder/mother helpers, assertion library already in use. Do not introduce a new mocking or assertion library without asking.
- Run the new tests (
dotnet test --nologo --filter <TestClassName>) and fix failures until green. - Report the coverage achieved and any behaviors you could not test without refactoring (and why).
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.
- 8d ago First seen · 23 lines · 37 tokens per session scan A 3d06cee6c03c
gen-tests is a skill published in the GitHub repository cwoodruff/dotnet-claude-workshop-content (2 stars, last pushed 1mo ago), licensed MIT. It adds 37 tokens to every session and 338 once invoked, about $0.0002 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
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…
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.
nw-fp-clojure
Clojure language-specific patterns, data-first modeling, REPL-driven development, and spec.
mobiai-ios-testing
Use when writing or running tests in an iOS project — unit tests, UI tests, snapshot tests, choosing the right framework.
restore-internals-seams-in-finally-blocks-after-each-test
When delegating a task affected by this skill, include.
testing-llm
LLM and AI testing patterns — mock responses, evaluation with DeepEval/RAGAS, structured output validation, and agentic test patterns (generator, healer, planner). Use when testing AI features, validating LLM outputs, or building evaluation pipelines.