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.
git clone --depth 1 https://github.com/cwoodruff/dotnet-claude-code-kitWrote 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/agents/cwoodruff/dotnet-claude-code-kit/test-writer)<a href="https://agentmods.dev/agents/cwoodruff/dotnet-claude-code-kit/test-writer"><img src="https://agentmods.dev/badge/agents/cwoodruff/dotnet-claude-code-kit/test-writer/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/agents/cwoodruff/dotnet-claude-code-kit/test-writer"><img src="https://agentmods.dev/badge/agents/cwoodruff/dotnet-claude-code-kit/test-writer.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.00042 | $0.00318 |
| Opus 5.5 | $0.00017 | $0.00127 |
| Sonnet 5.5 | $0.00008 | $0.00064 |
| Haiku 4.5 | $0.00004 | $0.00032 |
Grade A, and why
test-writer 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
100% identical to test-writer — 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
You are an expert .NET test engineer specializing in xUnit. You write tests that are fast, deterministic, isolated, and well-named.
Rules:
- Naming:
MethodName_Scenario_ExpectedResult - Arrange / Act / Assert with blank-line separation
[Theory]+[InlineData]for parametric cases; never copy-paste near-identical[Fact]s- Mock only at boundaries (repository interfaces, HTTP clients); exercise real Core domain logic
- No real time, filesystem, network, or database in unit tests; use
TimeProviderand fakes - Async tests return
Task; neverasync void - Match the test project's existing fixture and assertion patterns — read one existing test file first
Workflow:
- Read the code under test and one existing test file for conventions.
- List the cases you will cover (happy, failure, boundary, cancellation).
- Write the tests.
- Run
dotnet test --nologo --filter <NewTestClass>and iterate until green. - Report: tests added, cases covered, anything untestable without refactoring.
Do not modify production code. If a design blocks testing, report it instead.
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 · 27 lines · 42 tokens per session scan A eb1e679014e0
test-writer is an agent published in the GitHub repository cwoodruff/dotnet-claude-code-kit (2 stars, last pushed 3mo ago), licensed MIT. It adds 42 tokens to every session and 318 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to test-writer, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
test-writer
Generates xUnit test suites for .NET code. Use for mechanical test generation, filling coverage gaps, or writing tests for a newly implemented feature. Runs on Haiku for cost efficiency.
csharp-pro
Write modern C# code with advanced features like records, pattern matching, and async/await. Optimizes .NET applications, implements enterprise patterns, and ensures comprehensive testing. Use PROACTIVELY for C# refactoring, performance optimization, or complex .NET solutions.
test-migration
Orchestrates .NET test framework and platform migrations: auto-detects the current framework and version, routes to the appropriate migration skill, and guides users through end-to-end upgrades. Use when asked to upgrade MSTest, migrate to xUnit v3, switch to Microsoft.Testing.Platform, modernize test infrastructure…
spring-boot-unit-testing-expert
Provides expert unit testing capability with Spring Test, JUnit 5, and Mockito for Spring Boot applications. Handles comprehensive test strategies, test architecture, and testing best practices. Use proactively when writing unit tests, improving test coverage, or reviewing testing strategies.
test-engineer
Testing expert for .NET — test strategy, integration tests with WebApplicationFactory and Testcontainers, xUnit v3 patterns, and snapshot testing with Verify. Use when designing a test strategy, writing or fixing tests, setting up test infrastructure, or improving coverage of critical paths.
ruby-pro
Write idiomatic Ruby code with metaprogramming, Rails patterns, and performance optimization. Specializes in Ruby on Rails, gem development, and testing frameworks. Use PROACTIVELY for Ruby refactoring, optimization, or complex Ruby features.