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 agentmods add skills/cwoodruff/dotnet-claude-code-kit/gen-testsnpx skills add cwoodruff/dotnet-claude-code-kit --skill gen-testsgit clone --depth 1 https://github.com/cwoodruff/dotnet-claude-code-kitWhat 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 | $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 3d 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
100% identical to gen-tests — 0 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.
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.
- 3d 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-code-kit (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. It is 100% identical to gen-tests, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
run-helix-tests
Submit and monitor .NET MAUI unit tests on Helix infrastructure. Supports running XAML, Resizetizer, Core, Essentials, and other unit test projects on distributed Helix queues.
write-tests
Write failing tests from requirements. Invoke for each todo before /implement.
dart-add-unit-test
Write and organize unit tests for functions, methods, and classes using package:test. Use when creating new logic or fixing bugs to ensure code remains correct and regression-free.
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.
dart-test
DART Test: unit tests, integration tests, CI validation, and debugging.
myco:runtime-bootstrap-and-test-isolation
Activate this skill when adding a new manager, adding a new tool category, writing or debugging tool unit tests, diagnosing tool-visibility failures, investigating startup performance, or extending/maintaining/debugging the two-tier tool discovery system (toolindex) — even if the user doesn't explicitly ask about the…