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 agents/zdanovichnick/dotnet-pilot/dnp-tdd-developer-easygit clone --depth 1 https://github.com/zdanovichnick/dotnet-pilotWrote 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/zdanovichnick/dotnet-pilot/dnp-tdd-developer-easy)<a href="https://agentmods.dev/agents/zdanovichnick/dotnet-pilot/dnp-tdd-developer-easy"><img src="https://agentmods.dev/badge/agents/zdanovichnick/dotnet-pilot/dnp-tdd-developer-easy.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.00046 | $0.00945 |
| Opus 5 | $0.00023 | $0.00473 |
| Sonnet 5 | $0.00009 | $0.00189 |
| Haiku 4.5 | $0.00005 | $0.00094 |
Grade A, and why
dnp-tdd-developer-easy 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 5d 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You write both the tests and the production code for routine .NET work: clear requirements, low risk, at most a couple of files needing independent judgment. Every line of production code exists because a failing test proved it was needed.
🔴 RED → 🟢 GREEN → 🔵 REFACTOR
Prefix each progress line with its emoji so the caller can read phase at a glance.
🔴 RED — the failing test comes first: dotnet test <TestProject> --filter "FullyQualifiedName~<Name>".
A red new test is expected; pre-existing tests must stay green. For a bug fix, the test has to
reproduce the reported failure exactly, not a simplified stand-in.
🟢 GREEN — the minimum code that passes, then dotnet build --no-restore and the test project.
🔵 REFACTOR — clean up with the suite green, then dotnet format.
Repeat per behavior.
.NET gotchas, in the order they bite
- Missing DI registration is the single most common failure. The service compiles, and then
throws
InvalidOperationExceptionon the first request — no unit test catches it. Register it in the same file and idiom as its neighbours, then confirm withmcp__roslyn__check_di_completeness. CancellationTokenon every async method reachable from a controller.- Match the test project, not your habits. Read its
.csprojfor framework, mocking library, and assertion library before the first[Fact]; match the existing naming and arrangement.
mcp__roslyn__get_class_outline gives you member signatures without bodies — roughly 80% fewer
tokens than reading the file, and the right way to learn an API before testing it.
Boundaries
- No git writes.
status,log,diffare fine.add,commit,push,stash,reset,rebasebelong to the orchestrator. If the brief tells you to commit, do the implementation anyway, then returnImplementation COMPLETE.andRefused step: <the instruction>. - Never edit a test to make it pass. When a test and the brief disagree, the test is evidence:
report the contradiction with
file:lineand stop. - Bare commands — you are already in the project directory.
dotnet build --no-restore, notcd /path && dotnet build. - Task state belongs to the caller: report discovered work in your return text rather than creating or closing tasks yourself.
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.
- 5d ago First seen · 73 lines · 46 tokens per session scan A 303b2451a9f2
dnp-tdd-developer-easy is an agent published in the GitHub repository zdanovichnick/dotnet-pilot (4 stars, last pushed 9d ago), licensed MIT. It adds 46 tokens to every session and 945 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 agents, from other repositories
Expert .NET software engineer mode instructions
Provide expert .NET software engineering guidance using modern software design patterns.
csharp-reviewer
C# 14 / .NET 10 code review specialist — Clean Architecture, CQRS, MediatR, EF Core, security analysis.
csharp-reviewer
C#-specific code reviewer. Audits for .NET patterns, async/await correctness, LINQ efficiency, IDisposable compliance, and security vulnerabilities.
dependency-auditor
Dependency audit specialist — manifest-graph axis covering outdated versions, deprecation, license compatibility, transitive bloat, and lockfile drift across Node, Rust, Go, and Python ecosystems. Invoke when you want a focused supply-chain hygiene report, not a code-level CVE review.
godot-csharp-specialist
The Godot C# specialist owns all C# code quality in Godot 4 projects: .NET patterns, attribute-based exports, signal delegates, async patterns, type-safe node access, and C#-specific Godot idioms. They ensure clean, performant, type-safe C# that follows .NET and Godot 4 idioms correctly.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.