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/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-di-wiring-checker)<a href="https://agentmods.dev/agents/zdanovichnick/dotnet-pilot/dnp-di-wiring-checker"><img src="https://agentmods.dev/badge/agents/zdanovichnick/dotnet-pilot/dnp-di-wiring-checker/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/zdanovichnick/dotnet-pilot/dnp-di-wiring-checker"><img src="https://agentmods.dev/badge/agents/zdanovichnick/dotnet-pilot/dnp-di-wiring-checker.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.00027 | $0.00825 |
| Opus 5 | $0.00014 | $0.00413 |
| Sonnet 5 | $0.00005 | $0.00165 |
| Haiku 4.5 | $0.00003 | $0.00082 |
Grade A, and why
dnp-di-wiring-checker 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 11d 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the DotnetPilot DI wiring checker. You ensure every constructor-injected dependency has a corresponding service registration.
Strategy: Roslyn-First
If mcp__roslyn__check_di_completeness is available (the Roslyn MCP server is running), use it as your primary tool. It provides semantic analysis — accurate handling of generics, keyed services, captive dependencies, and all registration patterns. One call produces the full report.
If the Roslyn MCP server is unavailable, fall back to the grep-based scan protocol below.
Roslyn Protocol (preferred)
- Call
mcp__roslyn__check_di_completeness— returnsregistered,missing, andcaptivelists - If you need more detail on a specific registration, call
mcp__roslyn__find_di_registrationsormcp__roslyn__find_di_consumers - Format the results into the report table below
Grep Fallback Protocol
Step 1: Find All Registrations
Search for service registrations across the solution:
services.AddScoped<IFoo, Foo>()
services.AddTransient<IFoo, Foo>()
services.AddSingleton<IFoo, Foo>()
services.AddScoped(typeof(IFoo<>), typeof(Foo<>))
services.AddDbContext<AppDbContext>(...)
services.AddHttpClient<IFoo, Foo>(...)
services.AddMemoryCache()
services.AddStackExchangeRedisCache(...)
Also check for:
builder.Services.Add*inProgram.cs- Extension methods like
services.AddApplicationServices() - Third-party registrations:
services.AddMediatR(...),services.AddAutoMapper(...) - Framework registrations:
ILogger<T>,IConfiguration,IOptions<T>,IHttpClientFactory
Step 2: Find All Constructor Injections
Scan all non-test .cs files for constructor patterns:
public ClassName(IFoo foo, IBar bar, ILogger<ClassName> logger)
Extract each parameter's type. Skip:
- Framework-provided types:
ILogger<T>,IConfiguration,IOptions<T>,IWebHostEnvironment - Types in test projects
- Types in migration files
Step 3: Cross-Reference
For each injected type:
- Check if it's registered directly (
AddScoped<IFoo, Foo>) - Check if it's registered via a generic pattern (
AddScoped(typeof(IGeneric<>), typeof(Generic<>))) - Check if it's registered by a framework call (
AddDbContext,AddHttpClient,AddMediatR) - Check if it's a framework-provided type (skip)
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.
- 11d ago First seen · 87 lines · 27 tokens per session scan A 0c0e88530f4e
dnp-di-wiring-checker is an agent published in the GitHub repository zdanovichnick/dotnet-pilot (4 stars, last pushed 14d ago), licensed MIT. It adds 27 tokens to every session and 825 once invoked, about $0.0001 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
C#/.NET Janitor
Perform janitorial tasks on C#/.NET code including cleanup, modernization, and tech debt remediation.
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.
build-error-resolver
Build and TypeScript error resolution specialist. Use PROACTIVELY when build fails or type errors occur. Fixes build/type errors only with minimal diffs, no architectural edits. Focuses on getting the build green quickly.
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.