java-inspector AGENTS.md

A TypeScript server that examines Java classes from Maven dependencies, using Vineflower to turn compiled classes back into readable Java source.

In plain words
What is it for?
Use it to scan project dependencies, decompile and analyse classes, search class contents, and inspect inheritance relationships. It requires Node.js, Java, and Maven.
Why use it?
It helps developers understand library code when the original source is unavailable or difficult to inspect directly.

Instructions file for CodexOpenCode

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 instructions/mustafagoksever/java-inspector/agents-md
Clone the repo
git clone --depth 1 https://github.com/mustafagoksever/java-inspector

Made for: Codex, OpenCode.

Per session 3,405 This file is loaded in full into every session.
When invoked 3,405 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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 $0.03405 $0.03405
Opus 5 $0.01702 $0.01702
Sonnet 5 $0.00681 $0.00681
Haiku 4.5 $0.00341 $0.00341

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

Security

Grade A, and why

java-inspector AGENTS.md 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.

AGENTS.md · 233 lines

How it starts

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

Agent Instructions — java-inspector

What this is

TypeScript MCP server that decompiles Java classes from Maven dependencies using Vineflower. Ships as an npm package with a bundled Vineflower JAR.

Developer commands

Task Command
Build (compile src/dist/) npm run build
Run dev (no build step) npm run dev (uses tsx)
Start built server npm start
Test npm test (Jest, currently no test files exist)
Publish prep npm run prepublishOnly (runs tsc)

Runtime requirements

  • Node.js ≥ 16
  • Java runtime (for Vineflower decompiler and javap)
  • Maven (for dependency:build-classpath scanning)

Architecture & entry points

File Role
src/index.ts MCP server (JavaClassAnalyzerMCPServer). Exposes 5 tools: scan_dependencies, decompile_class, analyze_class, search_class, get_inheritance_tree
src/cli.ts Commander CLI. Default action (no args) starts the MCP server
src/cache/ProjectCache.ts Cache I/O: JSONL append-only persistence, in-memory Map index, pom/classpath hash validation, cross-process file locking via proper-lockfile
src/scanner/DependencyScanner.ts Runs mvn dependency:build-classpath, parses JAR paths. Singleton. Integrates BackgroundScanner + LazyResolver
src/scanner/BackgroundScanner.ts Background batch parallel JAR scanning (20 JARs at a time). Writes to JSONL incrementally
src/scanner/LazyResolver.ts On-demand class resolution: O(1) memory lookup, parallel JAR search on cache miss
src/decompiler/DecompilerService.ts Extracts .class from JARs (via yauzl), runs Vineflower (java -jar vineflower.jar <class> <outdir>). Reads generated .java from output dir and cleans up temp files
src/analyzer/JavaClassAnalyzer.ts Runs javap -v -cp <jar> <class> and parses the text output
src/utils/methodExtractor.ts Extracts a single method body from decompiled source via regex + brace matching. Handles strings, line/block comments, nested braces, and abstract methods.
src/utils/cachePaths.ts Cache lives under ~/.cache/java-inspector/<project>_<hash>/

Read the full file on GitHub · 233 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. 2d ago First seen · 233 lines · 3,405 tokens per session scan A 5362ceb37241

Subscribe to this mod's changes

java-inspector AGENTS.md is an instructions file published in the GitHub repository mustafagoksever/java-inspector (1 stars, last pushed 11d ago), licensed Apache-2.0. It adds 3,405 tokens to every session, about $0.0170 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.