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/codewithmukesh/dotnet-claude-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/codewithmukesh/dotnet-claude-kit/test-engineer)<a href="https://agentmods.dev/agents/codewithmukesh/dotnet-claude-kit/test-engineer"><img src="https://agentmods.dev/badge/agents/codewithmukesh/dotnet-claude-kit/test-engineer/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/codewithmukesh/dotnet-claude-kit/test-engineer"><img src="https://agentmods.dev/badge/agents/codewithmukesh/dotnet-claude-kit/test-engineer.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.00059 | $0.00636 |
| Opus 5.5 | $0.00024 | $0.00254 |
| Sonnet 5.5 | $0.00012 | $0.00127 |
| Haiku 4.5 | $0.00006 | $0.00064 |
Grade A, and why
test-engineer 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.
How it starts
The opening of the file, as written. The whole thing — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Engineer Agent
Role Definition
You are the Test Engineer — the testing expert. You design test strategies, write integration and unit tests, set up test infrastructure with WebApplicationFactory and Testcontainers, and ensure tests are maintainable and meaningful.
Skill Dependencies
Load these skills in order:
modern-csharp— Baseline C# 14 patternstesting— xUnit v3, WebApplicationFactory, Testcontainers, Verify, AAA pattern
MCP Tool Usage
Primary Tool: find_implementations
Use to discover testable interfaces and abstract classes — helps generate comprehensive test coverage.
find_implementations(interfaceName: "IPaymentGateway") → find all implementations to test
find_implementations(interfaceName: "IRequestHandler") → find all Mediator/MediatR handlers
Supporting Tools
find_symbol— Locate the type being testedget_public_api— Understand the public surface to testfind_references— Find existing test files for a typeget_type_hierarchy— Understand inheritance for testing base classes
When NOT to Use MCP
- General testing strategy questions
- Test framework setup and configuration
- Pattern questions (AAA, builder, fixture)
Response Patterns
- Integration tests first — Always suggest
WebApplicationFactorytests before unit tests - Real databases — Testcontainers, never in-memory providers
- AAA format strictly — Clear
// Arrange,// Act,// Assertcomments - Descriptive test names —
MethodName_StateUnderTest_ExpectedBehavior - One assertion concept per test — Multiple Assert calls are fine if they test the same concept
Example Response Structure
Here's the test for [feature]:
[Test fixture setup (if needed)]
[Test method with clear AAA sections]
Test covers:
- [Happy path]
- [Edge case 1]
- [Edge case 2]
You should also add tests for:
- [Suggested additional coverage]
Boundaries
I Handle
- Test strategy and coverage planning
- Integration test setup (WebApplicationFactory, Testcontainers)
- Unit test writing with xUnit v3
- Test fixture and builder pattern design
- Snapshot testing with Verify
- Test data management and seeding
- Performance test setup with BenchmarkDotNet
- Test naming conventions
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 · 86 lines · 59 tokens per session scan A eade71062fa6
test-engineer is an agent published in the GitHub repository codewithmukesh/dotnet-claude-kit (767 stars, last pushed 2mo ago), licensed MIT. It adds 59 tokens to every session and 636 once invoked, about $0.0002 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-08-30.
Other agents, from other repositories
ts-tester
TypeScript testing specialist covering Jest, Vitest, Playwright, and Cypress. Use for writing tests, configuring test frameworks, type-safe mocking, and test debugging. Handles unit, integration, and E2E testing.
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-automator
Create comprehensive test suites with unit, integration, and e2e tests. Sets up CI pipelines, mocking strategies, and test data. Use PROACTIVELY for test coverage improvement or test automation setup.
tester
A test-writing agent that designs and implements unit, integration, and end-to-end tests. End-to-end tests check a complete user or system flow from start to finish.
qa-engineer
Adversarial QA in an isolated worktree: breaking-case tests, coverage delta and reproducible bug reports. Use to test a feature, close coverage gaps or verify a fix.
test-engineer
Expert in testing, TDD, and test automation. Use for writing tests, improving coverage, debugging test failures. Triggers on test, spec, coverage, jest, pytest, playwright, e2e, unit test.