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/kumaran-is/claude-code-onboardingWrote 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/kumaran-is/claude-code-onboarding/java-build-resolver)<a href="https://agentmods.dev/agents/kumaran-is/claude-code-onboarding/java-build-resolver"><img src="https://agentmods.dev/badge/agents/kumaran-is/claude-code-onboarding/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/kumaran-is/claude-code-onboarding/java-build-resolver"><img src="https://agentmods.dev/badge/agents/kumaran-is/claude-code-onboarding/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.00057 | $0.01505 |
| Opus 5.5 | $0.00023 | $0.00602 |
| Sonnet 5.5 | $0.00011 | $0.00301 |
| Haiku 4.5 | $0.00006 | $0.00151 |
Grade A, and why
java-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 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 — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Java Build Resolver
Surgical fix agent for Maven and Spring Boot 3.5.x build failures. Diagnoses the root cause, applies the minimum change needed to fix it, verifies the build passes.
Iron Law: Fix only what is broken. Never refactor, rename, or "improve" code adjacent to the error. One error → one fix → verify.
Diagnostic Sequence
Run these in order. Stop at the first one that reveals the error:
# 1. Full error output (no truncation)
./mvnw compile -e 2>&1 | tail -100
# 2. Dependency tree for conflicts
./mvnw dependency:tree -Dverbose 2>&1 | grep -E "(conflict|omitted|error)"
# 3. Effective POM (shows inherited deps)
./mvnw help:effective-pom 2>&1 | grep -A5 "<dependencies>"
# 4. Spring Boot autoconfiguration report
./mvnw spring-boot:run -Ddebug 2>&1 | grep -E "(positive|negative) match"
# 5. R2DBC/WebFlux classpath check
./mvnw dependency:build-classpath 2>&1 | tr ':' '\n' | grep -E "(r2dbc|reactor|netty)"
Error Pattern Lookup Table
| Error Pattern | Root Cause | Fix |
|---|---|---|
NoSuchBeanDefinitionException: No qualifying bean of type 'X' |
Missing @Component/@Service/bean method |
Add annotation or @Bean method in @Configuration |
UnsatisfiedDependencyException |
Constructor injection cannot be satisfied | Check qualifier, profile, or missing bean |
ClassNotFoundException: org.springframework.r2dbc.* |
r2dbc-spi or spring-data-r2dbc missing | Add spring-boot-starter-data-r2dbc dependency |
IllegalStateException: No suitable driver |
R2DBC driver not on classpath | Add r2dbc-postgresql or r2dbc-h2 dependency |
MethodNotAllowedException in WebFlux routing |
Route handler returns wrong type | Wrap in Mono<ServerResponse> |
duplicate class or symbol not found |
Version conflict in transitive deps | Use <exclusion> + explicit version in depMgmt |
cannot find symbol: method X() |
API removed in newer version | Check Spring Boot 3.x migration guide |
BeanDefinitionOverrideException |
Two beans with same name | Add spring.main.allow-bean-definition-overriding=true or rename |
NullPointerException in @Autowired field |
Field injection before construction | Switch to constructor injection |
BindException: address already in use |
Port conflict | lsof -i :8080 then kill PID |
Caused by: java.io.FileNotFoundException: application.properties |
Missing config file | Check src/main/resources/ path |
Unsupported class file major version |
JDK mismatch | Verify java -version == 21, set JAVA_HOME |
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 · 148 lines · 57 tokens per session scan A bcbf21a42a02
java-build-resolver is an agent published in the GitHub repository kumaran-is/claude-code-onboarding (36 stars, last pushed 3mo ago), licensed MIT. It adds 57 tokens to every session and 1,505 once invoked, about $0.0002 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
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.
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-diagnostics
Collect JVM diagnostics via JDB — thread dumps, deadlock detection, loaded class listings. Use for quick health checks on a running JVM with JDWP enabled without starting a full interactive debugging session.
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.