Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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/skills/zhang-henry/coevoskills/evo-java-build-fixer)<a href="https://agentmods.dev/skills/zhang-henry/coevoskills/evo-java-build-fixer"><img src="https://agentmods.dev/badge/skills/zhang-henry/coevoskills/evo-java-build-fixer.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.1 | $0.00052 | $0.00683 |
| Opus 5 | $0.00026 | $0.00342 |
| Sonnet 5 | $0.00010 | $0.00137 |
| Haiku 4.5 | $0.00005 | $0.00068 |
Grade A, and why
evo-java-build-fixer 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 8d 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Java Build Fixer Skill
This skill diagnoses and fixes Java Maven build failures, particularly those caused by Java version incompatibilities in CI environments (e.g., tools.jar missing in Java 9+).
Workflow
- Discover the repository under
/home/travis/build/failed/ - Run the build to capture error output
- Parse Maven errors to identify root cause
- Analyze dependency trees for problematic transitive dependencies
- Write analysis to
failed_reasons.txt - Generate minimal unified diff patches
- Apply patches to fix the build
- Verify the build passes
Key Functions
find_repo_dir()- Discovers the repository pathfind_build_command()- Extracts build command from .travis.ymlrun_build()- Executes the build and captures outputparse_maven_errors()- Categorizes Maven error outputdetect_tools_jar_issue()- Identifies Java 9+ tools.jar problemsfind_tools_jar_dependency_sources()- Finds POMs with tools.jar dependenciesadd_exclusion_to_dependency()- Adds Maven exclusion blocks to POM dependenciesgenerate_diff()- Creates proper unified diffs using thediffcommandfix_tools_jar_issue()- Generates patches for tools.jar problemsapply_patch()- Applies patches using thepatchcommandrun_end_to_end()- Full pipeline from discovery to verificationvalidate_output()- Validates all required output files exist and are correct
Usage Example
import sys
sys.path.insert(0, '/app/environment/skills/evo-java-build-fixer/scripts')
from utils import run_end_to_end, validate_output
# Run the full pipeline
success = run_end_to_end(base_path='/home/travis/build/failed', build_timeout=300)
print(f"Build fix {'succeeded' if success else 'may need manual review'}")
# Validate outputs
valid = validate_output(base_path='/home/travis/build/failed')
print(f"Validation: {'PASS' if valid else 'FAIL'}")
Common Build Failure Patterns
tools.jar Missing (Java 9+)
Libraries like compile-testing depend on com.sun:tools with a system scope
pointing to tools.jar. In Java 9+, this file was removed. Fix by adding
<exclusion> blocks for com.sun:tools in the affected dependencies.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago First seen · 69 lines · 52 tokens per session scan A d70cad4d9bb9
evo-java-build-fixer is a skill published in the GitHub repository Zhang-Henry/CoEvoSkills (65 stars, last pushed 18d ago), licensed Apache-2.0. It adds 52 tokens to every session and 683 once invoked, about $0.0003 per session on Opus 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 skills, from other repositories
nullaway
Guide for resolving NullAway static analysis errors. Best practices for: Passing ObservableSupplier/Supplier Dereferencing potentially @Nullable values Adding @NullMarked to Java code.
wxjava-troubleshooter
A troubleshooting guide for WxJava, a Java library used to connect applications to WeChat services. It organizes problems involving setup, access tokens, signatures, payment certificates, callbacks, data conversion, network requests, and multiple accounts.
performance-smell-detection
Detect potential code-level performance smells in Java - streams, collections, boxing, regex, object creation. Provides awareness, not absolutes - always measure before optimizing. For JPA/database performance, use jpa-patterns instead.
126-java-exception-handling
Use when you need to apply Java exception handling best practices — including using specific exception types, managing resources with try-with-resources, securing exception messages, preserving error context via exception chaining, validating inputs early with fail-fast principles, handling thread interruption…
jstall
This skill should be used when the user asks about "JVM performance", "Java thread dump", "Java deadlock", "JVM diagnosis", "what is my Java application doing", "slow Java", "Java profiling", "flamegraph", "Java CPU usage", "thread contention", "JVM inspection", "jstall", or any question about analyzing, debugging, or…
java-heap-dump-triage
A guide for investigating Java memory problems using heap dumps and related reports. A heap dump is a snapshot of objects held in the Java Virtual Machine's memory.