maven-dependency-upgrader

maven-dependency-upgrader is a skill for Codex from Jiangxianze/spring-agent-skills. It costs 60 tokens per session (523 once invoked), scanned A, original, Apache-2.0.

A guide for planning and checking upgrades to Maven dependencies and build tools in Java projects. Maven is the tool that downloads libraries and builds Java code; BOMs are files that keep related library versions compatible.

In plain words
What is it for?
Use it to assess version drift, fix vulnerable dependencies, plan Spring or Java upgrades, resolve dependency conflicts, and sequence changes in projects with multiple modules.
Why use it?
It helps prevent upgrades from causing build failures, security problems, removed-API errors, or incompatible combinations of Java and Spring versions.

Skill for Codex

Written for Codex: agents/openai.yaml present.

Good fit Use it to assess version drift, fix vulnerable dependencies, plan Spring or Java upgrades, resolve dependency conflicts, and sequence changes in projects with multiple modules.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/jiangxianze/spring-agent-skills/maven-dependency-upgrader
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.

Any agent
npx skills add Jiangxianze/spring-agent-skills --skill maven-dependency-upgrader
Clone the repo
git clone --depth 1 https://github.com/Jiangxianze/spring-agent-skills

Made for: Codex.

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.

agentmods badge for maven-dependency-upgrader

README.md
[![agentmods](https://agentmods.dev/badge/skills/jiangxianze/spring-agent-skills/maven-dependency-upgrader/github.svg)](https://agentmods.dev/skills/jiangxianze/spring-agent-skills/maven-dependency-upgrader)
Your own site
<a href="https://agentmods.dev/skills/jiangxianze/spring-agent-skills/maven-dependency-upgrader"><img src="https://agentmods.dev/badge/skills/jiangxianze/spring-agent-skills/maven-dependency-upgrader/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.

agentmods 80×15 button for maven-dependency-upgrader

Your own site · 80×15
<a href="https://agentmods.dev/skills/jiangxianze/spring-agent-skills/maven-dependency-upgrader"><img src="https://agentmods.dev/badge/skills/jiangxianze/spring-agent-skills/maven-dependency-upgrader.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 60 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 523 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original 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.1 $0.00060 $0.00523
Opus 5 $0.00030 $0.00262
Sonnet 5 $0.00012 $0.00105
Haiku 4.5 $0.00006 $0.00052

Measured 11d ago against content hash 88c1f44b8478, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

maven-dependency-upgrader 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 11d 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.

skills/maven-dependency-upgrader/SKILL.md · 46 lines

How it starts

The opening of the file, as written. The whole thing — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Maven Dependency Upgrader

Upgrade the smallest coherent version set while preserving a reproducible baseline and a fast rollback path.

Capture the baseline

  1. Record Java and Maven versions, active profiles, repository mirrors, wrapper version, and the exact failing or passing command.
  2. Read the reactor POMs, imported BOMs, parent POM, plugin management, and dependency management before editing leaf versions.
  3. Run the existing build and save relevant test, dependency convergence, and application startup results.
  4. Generate the effective POM and dependency tree for disputed artifacts. Distinguish declared, managed, and transitive versions.

Plan the upgrade

  1. Identify the version owner. Prefer a framework or platform BOM over scattered explicit versions.
  2. Check the target's Java baseline, removed APIs, configuration changes, database driver behavior, bytecode tooling, and build-plugin requirements.
  3. Keep framework families compatible. Treat Spring Boot, Spring Cloud, Spring AI, Hibernate, Jackson, Netty, Kotlin, and test libraries as coordinated sets when their compatibility guidance requires it.
  4. Split unrelated upgrades. Upgrade build prerequisites first, the platform next, adapters after that, and application code last.
  5. For security remediation, verify the resolved artifact version rather than assuming a direct declaration wins.

Validate each batch

Run the smallest relevant module tests first, then the full reactor. Include dependency convergence, integration tests, packaging, startup smoke tests, and native or container builds when the project uses them. Compare runtime behavior, not only compilation.

Do not delete tests, exclusions, enforcer rules, or compiler warnings merely to obtain a green build. Explain any temporary compatibility shim and its removal condition.

Output contract

Provide:

  • baseline and target versions with their version owner;
  • compatibility constraints and evidence found in the repository;
  • an ordered, reviewable change plan;
  • exact validation commands and observed results;
  • remaining risks, rollback commit or version, and follow-up cleanup.

Read the full file on GitHub · 46 lines

Files

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.

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. 11d ago First seen · 46 lines · 60 tokens per session scan A 88c1f44b8478

Subscribe to this mod's changes

maven-dependency-upgrader is a skill published in the GitHub repository Jiangxianze/spring-agent-skills (1 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 60 tokens to every session and 523 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.

Related

Other skills, from other repositories

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-contrib/neo4j-skills · 154 tokens

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…

neo4j-contrib/neo4j-skills · 148 tokens

java-coding-standards

Java coding standards for Spring Boot services: naming, immutability, Optional usage, streams, exceptions, generics, and project layout.

Jamkris/everything-gemini-code · 35 tokens

java-springboot-development

CIEL's framework for Java 17+ and Spring Boot 3+ development, security, and TDD.

jxoesneon/Ciel · 29 tokens

rules-quarkus

Expert knowledge for building Quarkus applications with Bazel using the rulesquarkus build system. Use when user asks about Quarkus+Bazel builds, augmentation, or troubleshooting.

kinhluan/rules-quarkus-skills · 42 tokens

database-patterns

Database patterns for JPA/Spring Data. Schema naming, Flyway migrations, N+1 prevention, transaction boundaries, indexing strategy.

pan94u/forge · 31 tokens