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 Jiangxianze/spring-agent-skills --skill spring-boot-failure-analyzergit clone --depth 1 https://github.com/Jiangxianze/spring-agent-skillsWrote 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/jiangxianze/spring-agent-skills/spring-boot-failure-analyzer)<a href="https://agentmods.dev/skills/jiangxianze/spring-agent-skills/spring-boot-failure-analyzer"><img src="https://agentmods.dev/badge/skills/jiangxianze/spring-agent-skills/spring-boot-failure-analyzer/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/jiangxianze/spring-agent-skills/spring-boot-failure-analyzer"><img src="https://agentmods.dev/badge/skills/jiangxianze/spring-agent-skills/spring-boot-failure-analyzer.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.00066 | $0.00626 |
| Opus 5 | $0.00033 | $0.00313 |
| Sonnet 5 | $0.00013 | $0.00125 |
| Haiku 4.5 | $0.00007 | $0.00063 |
Grade A, and why
spring-boot-failure-analyzer 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 10d 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 — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spring Boot Failure Analyzer
Find the first actionable cause of a Spring Boot startup failure, propose the smallest safe change, and define a command that proves the fix.
Workflow
- Preserve the complete exception chain and the first
APPLICATION FAILED TO STARTblock. Treat the final exception as a symptom until the earliest application-owned cause is identified. - Identify the build tool, Java version, Spring Boot version, active profiles, launch command, and whether the failure reproduces in a test.
- Classify the failure as configuration binding, bean construction, dependency cycle, conditional auto-configuration, classpath linkage, external resource, web-server binding, or test-slice mismatch.
- Inspect only the files that can participate in that category. Prefer source, configuration, and build metadata over guesses based on exception names.
- Gather one decisive piece of evidence. Use a focused test,
--debugcondition report, property binding trace, dependency tree, or port/process check as appropriate. - Propose one minimal fix. Preserve the application's intended boundaries; do not mask the failure with broad exclusions, optional injection, lazy initialization, or a disabled validation rule unless that behavior is explicitly intended.
- Re-run the narrowest failing command, then one broader build check. Report both results.
Evidence rules
- Separate observations from hypotheses.
- Quote the property path, bean name, condition, missing class, or occupied port that proves the diagnosis.
- Prefer the deepest application-owned
Caused byentry over framework wrapper exceptions. - Check whether environment variables override YAML or properties before editing a configuration file.
- For
NoSuchMethodError,ClassNotFoundException, andNoClassDefFoundError, inspect the resolved dependency graph and BOM alignment before changing application code. - For missing beans, inspect component scanning, configuration conditions, qualifiers, generics, and test slices before adding a new bean.
- For cycles, identify the architectural dependency loop. Do not recommend
spring.main.allow-circular-references=trueas the primary fix.
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.
- 10d ago First seen · 45 lines · 66 tokens per session scan A b4ad38cbff13
spring-boot-failure-analyzer is a skill published in the GitHub repository Jiangxianze/spring-agent-skills (1 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 66 tokens to every session and 626 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-31.
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…
neo4j-driver-java-skill
Neo4j Java Driver v6 — driver lifecycle, Maven/Gradle setup, executableQuery, executeRead/Write managed transactions, explicit transactions, async/reactive patterns, error handling, data type mapping, connection pool tuning, causal consistency/bookmarks. Use when writing Java or Kotlin code that connects to Neo4j via…
neo4j-spring-data-skill
Use when building Spring Boot applications with Neo4j using Spring Data Neo4j (SDN 7.x/8.x) — @Node entity mapping, @Relationship, @RelationshipProperties, Neo4jRepository, ReactiveNeo4jRepository, @Query annotations, application.yml configuration, projections, Neo4jClient, Neo4jTemplate, transactions, auditing, or…