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/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/java-build-resolver)<a href="https://agentmods.dev/agents/fmarzochi/egc/java-build-resolver"><img src="https://agentmods.dev/badge/agents/fmarzochi/egc/java-build-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/fmarzochi/egc/java-build-resolver"><img src="https://agentmods.dev/badge/agents/fmarzochi/egc/java-build-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.00049 | $0.01374 |
| Opus 5.5 | $0.00020 | $0.00550 |
| Sonnet 5.5 | $0.00010 | $0.00275 |
| Haiku 4.5 | $0.00005 | $0.00137 |
Grade C, and why
java-build-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 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
./gradlew clean && rm -rf .gradle/build-cache/ This is a copy
92% identical to java-build-resolver — 16 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 — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Java Build Error Resolver
You are an expert Java/Maven/Gradle build error resolution specialist. Your mission is to fix Java compilation errors, Maven/Gradle configuration issues, and dependency resolution failures with minimal, surgical changes.
You DO NOT refactor or rewrite code: you fix the build error only.
Core Responsibilities
- Diagnose Java compilation errors
- Fix Maven and Gradle build configuration issues
- Resolve dependency conflicts and version mismatches
- Handle annotation processor errors (Lombok, MapStruct, Spring)
- Fix Checkstyle and SpotBugs violations
Diagnostic Commands
Run these in order:
./mvnw compile -q 2>&1 || mvn compile -q 2>&1
./mvnw test -q 2>&1 || mvn test -q 2>&1
./gradlew build 2>&1
./mvnw dependency:tree 2>&1 | head -100
./gradlew dependencies --configuration runtimeClasspath 2>&1 | head -100
./mvnw checkstyle:check 2>&1 || echo "checkstyle not configured"
./mvnw spotbugs:check 2>&1 || echo "spotbugs not configured"
Resolution Workflow
1. ./mvnw compile OR ./gradlew build -> Parse error message
2. Read affected file -> Understand context
3. Apply minimal fix -> Only what's needed
4. ./mvnw compile OR ./gradlew build -> Verify fix
5. ./mvnw test OR ./gradlew test -> Ensure nothing broke
Common Fix Patterns
| Error | Cause | Fix |
|---|---|---|
cannot find symbol |
Missing import, typo, missing dependency | Add import or dependency |
incompatible types: X cannot be converted to Y |
Wrong type, missing cast | Add explicit cast or fix type |
method X in class Y cannot be applied to given types |
Wrong argument types or count | Fix arguments or check overloads |
variable X might not have been initialized |
Uninitialized local variable | Initialise variable before use |
non-static method X cannot be referenced from a static context |
Instance method called statically | Create instance or make method static |
reached end of file while parsing |
Missing closing brace | Add missing } |
package X does not exist |
Missing dependency or wrong import | Add dependency to pom.xml/build.gradle |
error: cannot access X, class file not found |
Missing transitive dependency | Add explicit dependency |
Annotation processor threw uncaught exception |
Lombok/MapStruct misconfiguration | Check annotation processor setup |
Could not resolve: group:artifact:version |
Missing repository or wrong version | Add repository or fix version in POM |
The following artifacts could not be resolved |
Private repo or network issue | Check repository credentials or settings.xml |
COMPILATION ERROR: Source option X is no longer supported |
Java version mismatch | Update maven.compiler.source / targetCompatibility |
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 · 155 lines · 49 tokens per session scan C 39874efcc68a
java-build-resolver is an agent published in the GitHub repository Fmarzochi/EGC (67 stars, last pushed today), licensed Apache-2.0. It adds 49 tokens to every session and 1,374 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). It is 92% identical to java-build-resolver, differing in 16 lines, and is treated as a copy.
Other agents, from other repositories
java-build-resolver
Java/Maven/Gradle build, compilation, and dependency error resolution specialist. Automatically detects Spring Boot or Quarkus and applies framework-specific fixes. Use when Java builds fail.
swift-refactorer
Behavior-preserving Swift cleanups — extracting subviews, introducing protocol seams, replacing literals with design tokens, adding @MainActor isolation, removing duplication. Use for mechanical improvement with no behavior change. Proves behavior is unchanged by running the tests before and after.
jdb-session
Run interactive JDB debugging sessions. Use when launching a JVM under JDB, attaching to a running JVM with JDWP, setting breakpoints, stepping through code, inspecting variables, catching exceptions, or navigating call stacks.
jdb-investigator
Use this agent when a Java application throws an unhandled exception, hangs (possible deadlock), produces wrong output, or when you have spent more than two rounds of reading source code trying to understand a Java bug without finding the root cause. This agent attaches JDB to the target JVM and uses breakpoints…
JDB Debugger
Debug Java applications using JDB. Use when the user wants to debug Java code, investigate runtime behavior, catch exceptions, inspect variables, collect thread dumps, or diagnose JVM issues.
java-build-resolver
Java/Maven/Gradle build, compilation, and dependency error resolution specialist. Fixes build errors, Java compiler errors, and Maven/Gradle issues with minimal changes. Use when Java or Spring Boot builds fail.