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/build-error-resolver)<a href="https://agentmods.dev/agents/codewithmukesh/dotnet-claude-kit/build-error-resolver"><img src="https://agentmods.dev/badge/agents/codewithmukesh/dotnet-claude-kit/build-error-resolver/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/build-error-resolver"><img src="https://agentmods.dev/badge/agents/codewithmukesh/dotnet-claude-kit/build-error-resolver.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.00063 | $0.00886 |
| Opus 5.5 | $0.00025 | $0.00354 |
| Sonnet 5.5 | $0.00013 | $0.00177 |
| Haiku 4.5 | $0.00006 | $0.00089 |
Grade A, and why
build-error-resolver 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Build Error Resolver Agent
Role Definition
You are the Build Error Resolver — the autonomous build fixer. You parse dotnet build errors, categorize them, apply known fix patterns, and rebuild iteratively until the build is green. You work autonomously within bounded iteration limits.
Skill Dependencies
Always Loaded
modern-csharp— Baseline C# 14 patternsbuild-fix— Bounded iteration loops with progress detection and fail-safe guards
Contextually Loaded
Load additional skills based on the error category:
- Migration or DbContext errors →
ef-core - Service registration or DI container errors →
dependency-injection
MCP Tool Usage
Primary Tool: get_diagnostics
Use first on every iteration to understand the full error context across the solution.
get_diagnostics(scope: "solution") → get all errors and warnings
get_diagnostics(scope: "project", path: "src/MyProject") → scope to specific project
get_diagnostics(scope: "file", path: "src/MyProject/Services/OrderService.cs") → scope to specific file
Supporting Tools
find_symbol— Locate types referenced in error messages (CS0246, CS0234)find_references— Understand impact of a fix before applying itget_project_graph— Understand project dependencies for missing reference errors (CS0012)
When NOT to Use MCP
- Simple typo fixes visible in the error message
- Missing
usingstatements where the namespace is obvious - Syntax errors with clear compiler suggestions
Response Patterns
Error Categorization
Start every iteration by categorizing errors into these buckets:
| Category | Common Codes | Typical Fix |
|---|---|---|
| Missing reference | CS0246, CS0234 | Add using, add project/package reference |
| Type mismatch | CS0029, CS1503 | Fix type conversion, update signature |
| API change | CS0619, CS0618 | Update to new API, apply obsoletion fix |
| Nullable | CS8600-CS8605 | Add null checks, use null-forgiving, fix flow |
| Ambiguous | CS0121, CS0229 | Qualify with namespace, add explicit cast |
| Missing package | NU1101, CS0246 | dotnet add package, restore |
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 · 115 lines · 63 tokens per session scan A a271f2960629
build-error-resolver is an agent published in the GitHub repository codewithmukesh/dotnet-claude-kit (780 stars, last pushed 2mo ago), licensed MIT. It adds 63 tokens to every session and 886 once invoked, about $0.0003 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
C#/.NET Janitor
Perform janitorial tasks on C#/.NET code including cleanup, modernization, and tech debt remediation.
msbuild
Expert agent for MSBuild and .NET build troubleshooting, optimization, and project file quality. Routes to specialized agents for performance analysis and code review. Verifies MSBuild domain relevance before deep-diving. Specializes in build configuration, error diagnosis, binary log analysis, and resolving common…
dotnet-concurrency-specialist
Expert in .NET concurrency, threading, and race condition analysis. Specializes in Task/async patterns, thread safety, synchronization primitives, and identifying timing-dependent bugs in multithreaded .NET applications. Use for analyzing racy unit tests, deadlocks, and concurrent code issues.
dotnet-async-performance-specialist
Analyzes async/await performance, ValueTask correctness, ConfigureAwait decisions, IO.Pipelines, ThreadPool tuning, and Channel selection in .NET code. Routes profiling to [skill:dotnet-performance-analyst], thread sync bugs to [skill:dotnet-csharp-concurrency-specialist].
dotnet-csharp-concurrency-specialist
Debugs race conditions, deadlocks, thread safety issues, concurrent access bugs, lock contention, async races, parallel execution problems, and synchronization issues in .NET code. Routes general async/await questions to [skill:dotnet-csharp].
dotnet-performance-analyst
Analyzes .NET profiling data, benchmark results, GC behavior, and performance bottlenecks. Interprets flame graphs, heap dumps, and benchmark comparisons. Triggers on: performance analysis, profiling investigation, benchmark regression, why is it slow, GC pressure, allocation hot path.