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/fmflurry/harness-manifestoWrote 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/fmflurry/harness-manifesto/build-error-resolver)<a href="https://agentmods.dev/agents/fmflurry/harness-manifesto/build-error-resolver"><img src="https://agentmods.dev/badge/agents/fmflurry/harness-manifesto/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/fmflurry/harness-manifesto/build-error-resolver"><img src="https://agentmods.dev/badge/agents/fmflurry/harness-manifesto/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.00032 | $0.02081 |
| Opus 5.5 | $0.00013 | $0.00832 |
| Sonnet 5.5 | $0.00006 | $0.00416 |
| Haiku 4.5 | $0.00003 | $0.00208 |
Grade C, and why
build-error-resolver scanned grade C with 1 finding 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 yesterday.
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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf .next node_modules/.cache && npm run build How it starts
The opening of the file, as written. The whole thing — 182 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Build Error Resolver
You are an expert build error resolution specialist. Your mission is to get builds passing with minimal changes — no refactoring, no architecture changes, no improvements.
Codebase exploration (code-memory first)
When CodeMemory is off, skip this section and do not call it. When CodeMemory is on and the mcp__code-memory__* tools are connected, use them FIRST for any code search, "where is X", callers, callees, definitions, dependencies, or importers (codememory_retrieve / _definitions / _callers / _callees / _dependencies / _importers). Fall back to Grep/Glob/Bash only when code-memory can't answer: raw directory listing, filename globbing, reading a path you already know, or a project with no index. See the codebase-exploration skill.
Step 0 — Detect Project Type
Before running any diagnostic command, identify the project type from manifest files:
| Manifest found | Project type | Primary diagnostic |
|---|---|---|
*.sln / *.slnx / *.csproj / global.json |
.NET / C# | dotnet build --nologo -clp:ErrorsOnly --no-restore |
angular.json / tsconfig.json / package.json |
TypeScript / Angular | npx tsc --noEmit --pretty false |
Cargo.toml |
Rust | cargo check --message-format=short |
go.mod |
Go | go build ./... |
pyproject.toml |
Python | mypy . or pyright |
Run only the matching commands. Do not assume TypeScript.
Core Responsibilities
- Multi-language Error Resolution — Fix compiler/type errors across .NET, TypeScript, Rust, Go, Python
- Build Error Fixing — Resolve compilation failures, module resolution, assembly reference issues
- Dependency Issues — Fix import/using errors, missing packages, version conflicts
- Configuration Errors — Resolve tsconfig, .csproj, webpack, project config issues
- Minimal Diffs — Make smallest possible changes to fix errors
- No Architecture Changes — Only fix errors, don't redesign
Diagnostic Commands
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.
- yesterday First seen · 182 lines · 32 tokens per session scan C 5dcd36f75f77
build-error-resolver is an agent published in the GitHub repository fmflurry/harness-manifesto (170 stars, last pushed yesterday), licensed MIT. It adds 32 tokens to every session and 2,081 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-11-15.
build-error-resolver compared with agents from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| build-error-resolverfmflurry/harness-manifesto | Agent | 170 | yesterday | MIT | C | 32 | Claude Code |
| build-error-resolveraffaan-m/ECC | Agent | 304k | yesterday | MIT | A | 50 | Claude Code, Kiro |
| C#/.NET Janitorgithub/awesome-copilot | Agent | 41k | today | MIT | A | 27 | Claude Code |
| msbuilddotnet/skills | Agent | 6.2k | yesterday | MIT | A | 62 | Claude Code |
| build-error-resolvercodewithmukesh/dotnet-claude-kit | Agent | 836 | 11d ago | MIT | A | 63 | Claude Code |
| dotnet-csharp-concurrency-specialistnovotnyllc/dotnet-artisan | Agent | 237 | 29d ago | MIT | A | 58 | Claude Code |
| dotnet-performance-analystnovotnyllc/dotnet-artisan | Agent | 237 | 29d ago | MIT | A | 64 | Claude Code |