java-code-verification

A tool for checking Java code for syntax errors and problems found during compilation.

In plain words
What is it for?
Use it to review Java changes and identify compile-time mistakes.
Why use it?
It helps catch code that Java will reject before you run or release it.

Skill for Claude CodeCodex

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.

agentmods
npx agentmods add skills/sachiewang/java-jdtls-mcp-server/java-verification
Any agent
npx skills add SachieWang/java-jdtls-mcp-server --skill java-verification
Clone the repo
git clone --depth 1 https://github.com/SachieWang/java-jdtls-mcp-server

Made for: Claude Code, Codex.

Per session 18 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 428 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin unknown 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 $0.00018 $0.00428
Opus 5 $0.00009 $0.00214
Sonnet 5 $0.00004 $0.00086
Haiku 4.5 $0.00002 $0.00043

Measured 2d ago against content hash b40998bc1b4b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

java-code-verification 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 2d 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/java-verification/SKILL.md · 47 lines

The source is not reproduced here

Licensed GPL-3.0

The repository is licensed GPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.

Read it on GitHub

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. 2d ago First seen · 47 lines · 18 tokens per session scan A b40998bc1b4b

Subscribe to this mod's changes

java-code-verification is a skill published in the GitHub repository SachieWang/java-jdtls-mcp-server (2 stars, last pushed 5mo ago), licensed GPL-3.0. It adds 18 tokens to every session and 428 once invoked, about $0.0001 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

vr-planner

Plans how to verify changes to an os-autoinst-distri-opensuse (OSADO) checkout. Use this skill when the user asks "how do I test my change", "what verification run (VR) should I do", "which openQA job should I clone", or "what's affected by my edit". Determines required unit tests, affected test modules, YAML…

mpagot/os-autoinst-distri-opensuse-skills · 90 tokens

openqa-log-analyzer

A specialized skill for analyzing openQA logs — triage failures, measure command timing, detect infrastructure lag, extract command output, and compare runs across multiple log files.

mpagot/os-autoinst-distri-opensuse-skills · 39 tokens

local-lint-test

Recommends the fastest local commands to validate edited OSADO code before pushing. Activate when the user asks "how do I check my code", "what should I run locally", "lint my changes", "does this compile", "run perltidy", "run perlcritic", "run a unit test", "check formatting", or after editing files to verify…

mpagot/os-autoinst-distri-opensuse-skills · 111 tokens

test-catalog

Add or audit a Perldoc documentation header on an OSADO test module following the test catalog standard. Use when a user asks to "add header", "document", or "add catalog header" to a Perl test module.

mpagot/os-autoinst-distri-opensuse-skills · 50 tokens

unit-test-wizard

Writes and reviews OSADO Perl unit tests for library modules in lib/. Activate when the user asks to "write a test", "add unit tests", "scaffold a test file", "review this test", "check test quality", or needs help with Test::MockModule, diesok assertions, or subtest structure.

mpagot/os-autoinst-distri-opensuse-skills · 70 tokens

git-commit

Helps write OSADO-compliant git commit messages for staged changes. Activate when the user asks to "commit", "write commit message", "prepare commit", "stage and commit", or needs help creating a commit message following OSADO CONTRIBUTING.md rules.

mpagot/os-autoinst-distri-opensuse-skills · 56 tokens