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 skills add OpenLAIR/OpenSkill --skill evo-maven-build-diagnosisgit clone --depth 1 https://github.com/OpenLAIR/OpenSkillWrote 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/openlair/openskill/evo-maven-build-diagnosis)<a href="https://agentmods.dev/skills/openlair/openskill/evo-maven-build-diagnosis"><img src="https://agentmods.dev/badge/skills/openlair/openskill/evo-maven-build-diagnosis/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/skills/openlair/openskill/evo-maven-build-diagnosis"><img src="https://agentmods.dev/badge/skills/openlair/openskill/evo-maven-build-diagnosis.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.00547 |
| Opus 5 | $0.00024 | $0.00273 |
| Sonnet 5 | $0.00010 | $0.00109 |
| Haiku 4.5 | $0.00005 | $0.00055 |
Grade A, and why
evo-maven-build-diagnosis 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 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.
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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
evo-maven-build-diagnosis
Diagnoses Java Maven build failures by analyzing error logs and .travis.yml configuration.
Key Functions
execute_maven_build(project_dir, goals, java_home, timeout_secs, pom_file)- Run Maven build via subprocessparse_compilation_errors(maven_log)- Extract compilation errors with file/line/col/messageparse_dependency_errors(maven_log)- Extract missing dependency artifactsparse_plugin_errors(maven_log)- Extract plugin execution failuresparse_pom_errors(maven_log)- Extract POM-related errors (missing files, invalid XML)parse_version_incompatibilities(maven_log)- Extract source/target version issuesdetect_java_version_from_pom(pom_path)- Read Java version from pom.xmlclassify_build_failure(maven_log)- Classify the primary failure typeanalyze_travis_yml(travis_yml_path)- Check .travis.yml for issues like wrong file referenceswrite_diagnosis_report(report_path, analysis_results, log_analysis, travis_analysis)- Write failed_reasons.txt
Usage
import sys
sys.path.insert(0, '/app/environment/skills/evo-maven-build-diagnosis/scripts')
from utils import (
execute_maven_build, classify_build_failure, analyze_travis_yml,
write_diagnosis_report, parse_compilation_errors, parse_pom_errors
)
# Analyze build logs
with open('build.log') as f:
log = f.read()
analysis = classify_build_failure(log)
# Check .travis.yml
travis = analyze_travis_yml('.travis.yml')
# Write report
write_diagnosis_report('failed_reasons.txt', analysis, log_analysis=analysis, travis_analysis=travis)
Common Error Patterns
- POM Configuration: Missing/wrong POM file references (e.g.,
build.pom.xmlvsbuild-pom.xml) - Version Incompatibility: Source/target version no longer supported by JDK
- Dependency Resolution: Missing artifacts, tools.jar not found in JDK 9+
- Compilation: Cannot find symbol, missing imports, missing method implementations
- Plugin Execution: Failed plugin goals
What ships with it
1 file 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.
- yesterday First seen · 52 lines · 49 tokens per session scan A 61d62b33254c
evo-maven-build-diagnosis is a skill published in the GitHub repository OpenLAIR/OpenSkill (88 stars, last pushed yesterday), licensed Apache-2.0. It adds 49 tokens to every session and 547 once invoked, about $0.0002 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-09-11.
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.