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/affaan-m/ecc/java-build-resolvergit clone --depth 1 https://github.com/affaan-m/ECCWhat 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.00041 | $0.01146 |
| Opus 5 | $0.00020 | $0.00573 |
| Sonnet 5 | $0.00008 | $0.00229 |
| Haiku 4.5 | $0.00004 | $0.00115 |
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 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.
./gradlew clean && rm -rf .gradle/build-cache/ Copies of this mod
1 near-identical copy found in the catalogue:
- java-build-resolver — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 127 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.
Framework Detection (run first)
cat pom.xml 2>/dev/null || cat build.gradle 2>/dev/null || cat build.gradle.kts 2>/dev/null
- If the build file contains
quarkus→ apply [QUARKUS] rules - If the build file contains
spring-boot→ apply [SPRING] rules - If neither is detected → use general Java rules only
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
Resolution Workflow
1. Detect framework (Spring Boot / Quarkus)
2. ./mvnw compile OR ./gradlew build -> Parse error message
3. Read affected file -> Understand context
4. Apply minimal fix -> Only what's needed
5. ./mvnw compile OR ./gradlew build -> Verify fix
6. ./mvnw test OR ./gradlew test -> Ensure nothing broke
Common Fix Patterns
General Java
| Error | Cause | Fix |
|---|---|---|
cannot find symbol |
Missing import, typo, missing dependency | Add import or dependency |
incompatible types |
Wrong type, missing cast | Add explicit cast or fix type |
method X 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 | Initialize variable before use |
package X does not exist |
Missing dependency or wrong import | Add dependency to build file |
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 |
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 · 127 lines · 41 tokens per session scan C 00b4313d0e19
java-build-resolver is an agent published in the GitHub repository affaan-m/ECC (245,028 stars, last pushed yesterday), licensed MIT. It adds 41 tokens to every session and 1,146 once invoked, about $0.0002 per session on Opus 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-08-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.