java-build-resolver

A resolver for Java build problems involving Maven or Gradle, tools that compile code and manage its libraries. It addresses compilation, dependency, and build errors with small changes.

In plain words
What is it for?
Use it when Java or Spring Boot builds fail because of compiler errors, missing or conflicting dependencies, or Maven and Gradle issues.
Why use it?
It helps turn failed Java or Spring Boot builds into working builds without making unnecessary edits.

Agent

Install

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.

agentmods
npx agentmods add agents/yaomeng1749/claude-code-digital-nomad-config-pack/java-build-resolver
Clone the repo
git clone --depth 1 https://github.com/Yaomeng1749/claude-code-digital-nomad-config-pack
Per session 49 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,364 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. Scan, not verified.
Origin unknown No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00049 $0.01364
Opus 5 $0.00024 $0.00682
Sonnet 5 $0.00010 $0.00273
Haiku 4.5 $0.00005 $0.00136

Measured 3d ago against content hash 99e05ac7d2a6, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 3d 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/
ClaudeCode-Config-Pack/claude-home/agents/java-build-resolver.md · 154 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

Changes

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.

  1. 3d ago First seen · 154 lines · 49 tokens per session scan C 99e05ac7d2a6

Subscribe to this mod's changes

java-build-resolver is an agent published in the GitHub repository Yaomeng1749/claude-code-digital-nomad-config-pack (4 stars, last pushed 4mo ago), with no licence file. It adds 49 tokens to every session and 1,364 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-31.

Related

Other agents, from other repositories

java-reviewer

Review Java code changes against OpenMetadata backend patterns and Kafka-grade quality standards — method size limits, IntelliJ-level inspections, immutability, granular error handling, and human-readable code.

open-metadata/OpenMetadata · 40 tokens

plinth-tech-lead

Tech lead for Java Enterprise Development. Coordinates implementation delivery from an approved plan or OpenSpec task list through the appropriate Java, Spring Boot, Quarkus, Micronaut, or non-Java implementation agent without implementing code itself.

jabrena/plinth · 52 tokens

spring-ai-expert

Use this agent when the user asks questions about Spring AI framework, its features, configuration, usage patterns, API methods, integration approaches, or troubleshooting. Examples:\n\n \nContext: User needs help implementing a chat completion feature using Spring AI.\nuser: "How do I set up a chat client with Spring…

spring-ai-community/spring-ai-agent-utils · 363 tokens

plinth-java-quarkus-coder

Implementation specialist for Quarkus projects. Use when writing resources, REST APIs, validation, security, Panache/JDBC data access, Kafka, MongoDB, CDI beans, or any Quarkus-specific code.

jabrena/plinth · 52 tokens

plinth-java-coder

Implementation specialist for Java projects. Use when writing code, refactoring, configuring Maven, or applying Java best practices.

jabrena/plinth · 29 tokens

java-security-expert

Expert security auditor specializing in DevSecOps, comprehensive cybersecurity, and compliance frameworks. Masters vulnerability assessment, threat modeling, secure authentication (OAuth2/OIDC), OWASP standards, cloud security, and security automation. Handles DevSecOps integration, compliance (GDPR/HIPAA/SOC2), and…

giuseppe-trisciuoglio/developer-kit · 85 tokens