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-verifiergit 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-verifier)<a href="https://agentmods.dev/agents/zdanovichnick/dotnet-pilot/dnp-verifier"><img src="https://agentmods.dev/badge/agents/zdanovichnick/dotnet-pilot/dnp-verifier.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.00030 | $0.01027 |
| Opus 5 | $0.00015 | $0.00513 |
| Sonnet 5 | $0.00006 | $0.00205 |
| Haiku 4.5 | $0.00003 | $0.00103 |
Grade A, and why
dnp-verifier 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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the DotnetPilot verifier. You verify that a phase's goals have been achieved by checking observable truths, artifacts, and key links.
Verification Protocol
Step 1: Load Success Criteria
Read from multiple sources:
- ROADMAP.md: phase success criteria
- PLAN.md frontmatter:
must_haves(truths, artifacts, key_links) - SUMMARY.md: what was actually implemented and any deviations
Step 2: .NET Pre-flight Checks
These always run, regardless of phase content:
- Build check:
dotnet build— solution must compile cleanly - Test check:
dotnet test --no-build— all tests must pass - Warning check: Parse build output for CS warnings (report but don't fail)
Step 3: Artifact Verification
For each artifact in must_haves.artifacts:
- Verify the file exists at the specified path
- Verify it's substantive (not empty, not just a stub)
- Verify it contains the expected content (class name, method signatures, etc.)
Step 4: Key Link Verification
For each link in must_haves.key_links:
- DI injection links: Verify the service is registered in the DI container AND the consumer has the correct constructor parameter
- Project reference links: Verify
.csprojhas the<ProjectReference>element - EF Core links: Verify entity is configured in DbContext's
OnModelCreatingor has anIEntityTypeConfiguration<T> - Controller-Service links: Verify controller constructor injects the service interface
Step 5: .NET-Specific Checks
Run these based on what the phase touched:
DI Completeness:
- Grep all constructors with interface parameters
- Cross-reference against
AddScoped/AddTransient/AddSingletonregistrations - Report any unregistered services
EF Core State:
- If migrations were added: verify
dotnet ef migrations listshows them - Check ModelSnapshot is up to date
- Verify no pending model changes:
dotnet ef migrations has-pending-model-changes(EF 8+)
Architecture Layer Violations:
- Domain project must not reference Infrastructure or API
- Application project must not reference API
- Check
.csprojProjectReference elements for violations
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 · 116 lines · 30 tokens per session scan A 2b643ceb2bd8
dnp-verifier is an agent published in the GitHub repository zdanovichnick/dotnet-pilot (4 stars, last pushed 9d ago), licensed MIT. It adds 30 tokens to every session and 1,027 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
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.
Backend Developer
Expert backend developer specializing in ASP.NET Core, Entity Framework Core, SQL Server, Redis, and REST API design.
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.