check-version-compatibility

check-version-compatibility is a skill for Claude Code from kirich1409/krozov-ai-tools. It costs 95 tokens per session (666 once invoked), scanned A, original, MIT.

A compatibility checker for Android Gradle Plugin, Gradle, Kotlin, and JDK versions, plus Spring Boot dependency versions. It also checks Spring Boot's managed dependency versions and possible javax-to-jakarta changes.

In plain words
What is it for?
It is for validating Android build toolchains, Spring Boot dependencies, and migrations from the older javax package namespace to jakarta.
Why use it?
It catches version combinations that do not work together and gives a suggested correction with an official reference.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the maven-mcp plugin — 21 skills, 2 hooks shipped together

Good fit It is for validating Android build toolchains, Spring Boot dependencies, and migrations from the older javax package namespace to jakarta.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/kirich1409/krozov-ai-tools/check-version-compatibility
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 kirich1409/krozov-ai-tools --skill check-version-compatibility
Clone the repo
git clone --depth 1 https://github.com/kirich1409/krozov-ai-tools

Made for: Claude Code.

Or install maven-mcp, the plugin that ships this one along with the rest of its 21 skills, 2 hooks.

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 check-version-compatibility

README.md
[![agentmods](https://agentmods.dev/badge/skills/kirich1409/krozov-ai-tools/check-version-compatibility/github.svg)](https://agentmods.dev/skills/kirich1409/krozov-ai-tools/check-version-compatibility)
Your own site
<a href="https://agentmods.dev/skills/kirich1409/krozov-ai-tools/check-version-compatibility"><img src="https://agentmods.dev/badge/skills/kirich1409/krozov-ai-tools/check-version-compatibility/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 check-version-compatibility

Your own site · 80×15
<a href="https://agentmods.dev/skills/kirich1409/krozov-ai-tools/check-version-compatibility"><img src="https://agentmods.dev/badge/skills/kirich1409/krozov-ai-tools/check-version-compatibility.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 95 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 666 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00095 $0.00666
Opus 5 $0.00048 $0.00333
Sonnet 5 $0.00019 $0.00133
Haiku 4.5 $0.00010 $0.00067

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

Security

Grade A, and why

check-version-compatibility 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.

plugins/maven-mcp/plugin/skills/check-version-compatibility/SKILL.md · 57 lines

How it starts

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

Check Version Compatibility

Validate whether a set of versions is mutually compatible: Android Gradle Plugin ↔ Gradle ↔ JDK, Kotlin Gradle Plugin ↔ Gradle/AGP, Spring Boot BOM-managed versions, and javax→jakarta migration need.

Steps

  1. Gather whichever of these the user is asking about:

    • android: {agp, gradle, kotlin, jdk} — any subset
    • springBoot: a version string
    • dependencies: [{groupId, artifactId, version?}, ...] (capped at 100 items) — checked against the Spring Boot BOM (when springBoot is set) and, when Spring Boot ≥ 3.0.0, flagged for javax→jakarta coordinate replacements
  2. Call check_version_compatibility with whichever of android, springBoot, dependencies, projectPath apply. At least one of android/springBoot/dependencies should be present — an empty call has nothing to validate.

  3. Present the result:

    • compatible: true with no conflicts → confirm compatibility plainly.
    • Each conflict: kind, requested, expected, suggestion, reference (an official doc URL) — always show the suggestion and reference together, never a bare "conflict".
    • Print any notes[] (coverage caveats) alongside the result, not as an afterthought.

Known limitations

Coverage is intentionally bounded — AGP 7.0–9.2 lines, KGP 1.9.20–2.4.0 bands, no published AGP max-Gradle (only min enforced), javax→jakarta is a coordinate heuristic (not a bytecode scanner), Spring Cloud release trains are not a separate matrix. State the specific gap when a requested version falls outside shipped coverage — never imply "compatible" from silence.

Constraints and non-goals

  • Not for applying the suggested version bumps — that's a normal edit; verify with /check-deps or a project build afterward.

Fallback (MCP unavailable only)

Check the official compatibility tables directly: Android Gradle Plugin release notes (developer.android.com) for AGP↔Gradle↔JDK, the Kotlin Gradle plugin compatibility guide for KGP↔Gradle/AGP, and the Spring Boot release notes / dependency versions page for BOM-managed versions. Do not guess a compatibility matrix from memory — this stack changes across releases.

Read the full file on GitHub · 57 lines

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 · 57 lines · 95 tokens per session scan A 22d24f7aee40

Subscribe to this mod's changes

check-version-compatibility is a skill published in the GitHub repository kirich1409/krozov-ai-tools (22 stars, last pushed 6d ago), licensed MIT. It adds 95 tokens to every session and 666 once invoked, about $0.0005 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-01.

Related

Other skills, from other repositories

debug-optimize-lcp

Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…

ChromeDevTools/chrome-devtools-mcp · 99 tokens

systematic-debugging

Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.

open-metadata/OpenMetadata · 37 tokens

diagnose

Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.

emdash-cms/emdash · 43 tokens

repro-admin

Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.

emdash-cms/emdash · 48 tokens

log-error-digest

Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…

zebbern/claude-code-guide · 71 tokens

byted-util-volcengine-detect-retry

An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.

bytedance/agentkit-samples · 101 tokens