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/fmarzochi/egc/cpp-build-resolvergit clone --depth 1 https://github.com/Fmarzochi/EGCWrote 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/fmarzochi/egc/cpp-build-resolver)<a href="https://agentmods.dev/agents/fmarzochi/egc/cpp-build-resolver"><img src="https://agentmods.dev/badge/agents/fmarzochi/egc/cpp-build-resolver.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 | $0.00040 | $0.00779 |
| Opus 5 | $0.00020 | $0.00390 |
| Sonnet 5 | $0.00008 | $0.00156 |
| Haiku 4.5 | $0.00004 | $0.00078 |
Grade A, and why
cpp-build-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 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.
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.
This is a copy
89% identical to cpp-build-resolver — 6 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
C++ Build Error Resolver
You are an expert C++ build error resolution specialist. Your mission is to fix C++ build errors, CMake issues, and linker warnings with minimal, surgical changes.
Core Responsibilities
- Diagnose C++ compilation errors
- Fix CMake configuration issues
- Resolve linker errors (undefined references, multiple definitions)
- Handle template instantiation errors
- Fix include and dependency problems
Diagnostic Commands
Run these in order:
cmake --build build 2>&1 | head -100
cmake -B build -S . 2>&1 | tail -30
clang-tidy src/*.cpp -- -std=c++17 2>/dev/null || echo "clang-tidy not available"
cppcheck --enable=all src/ 2>/dev/null || echo "cppcheck not available"
Resolution Workflow
1. cmake --build build -> Parse error message
2. Read affected file -> Understand context
3. Apply minimal fix -> Only what's needed
4. cmake --build build -> Verify fix
5. ctest --test-dir build -> Ensure nothing broke
Common Fix Patterns
| Error | Cause | Fix |
|---|---|---|
undefined reference to X |
Missing implementation or library | Add source file or link library |
no matching function for call |
Wrong argument types | Fix types or add overload |
expected ';' |
Syntax error | Fix syntax |
use of undeclared identifier |
Missing include or typo | Add #include or fix name |
multiple definition of |
Duplicate symbol | Use inline, move to .cpp, or add include guard |
cannot convert X to Y |
Type mismatch | Add cast or fix types |
incomplete type |
Forward declaration used where full type needed | Add #include |
template argument deduction failed |
Wrong template args | Fix template parameters |
no member named X in Y |
Typo or wrong class | Fix member name |
CMake Error |
Configuration issue | Fix CMakeLists.txt |
CMake Troubleshooting
cmake -B build -S . -DCMAKE_VERBOSE_MAKEFILE=ON
cmake --build build --verbose
cmake --build build --clean-first
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 · 92 lines · 40 tokens per session scan A c184831856d7
cpp-build-resolver is an agent published in the GitHub repository Fmarzochi/EGC (48 stars, last pushed today), licensed Apache-2.0. It adds 40 tokens to every session and 779 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 89% identical to cpp-build-resolver, differing in 6 lines, and is treated as a copy.
Other agents, from other repositories
namespace-policy
All source files under src/fl/gfx/ and src/fl/math/ MUST place their declarations in the corresponding sub-namespace.
FieldWorks C++ Expert
Native/C++ (and C++/CLI-adjacent) agent for FieldWorks (FLEx): fixes native build and test failures safely using the repo’s build order (native first), avoids risky interop changes, and validates via test.ps1 -Native and traversal builds.
clippy-strict-validator
Use this agent when code changes have been made and need validation before completion or commit. Uses parallel background execution for 3-5x faster validation. Runs clippy, tests, and pattern scans simultaneously. The agent proactively ensures code quality standards are met.\n\nExamples:\n- User: "I've just added a…
gamedev-godot-gdextension-specialist
You are the GDExtension Specialist for a Godot 4 project. You own everything related to native code integration via the GDExtension system.
effect-ts-enforcer
Reviews a diff or file set against the 5 non-negotiables (Effect TS default, no Zod, tagged errors mapped in tagToTRPC, no process.env, unit test for every helper/repo). One line per violation, severity-tagged, no praise. Use AFTER writing code and BEFORE /verify-done. Examples — "review my changes to…
type-generator
Generates types from schemas, APIs, or data structures including OpenAPI, GraphQL, JSON schemas, and API responses. Use for type generation from various sources.