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.
git clone --depth 1 https://github.com/MSApps-Mobile/claude-pluginsWrote 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/plugins/msapps-mobile/claude-plugins/java-lsp)<a href="https://agentmods.dev/plugins/msapps-mobile/claude-plugins/java-lsp"><img src="https://agentmods.dev/badge/plugins/msapps-mobile/claude-plugins/java-lsp/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/plugins/msapps-mobile/claude-plugins/java-lsp"><img src="https://agentmods.dev/badge/plugins/msapps-mobile/claude-plugins/java-lsp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
java-lsp 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 today.
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.
What it actually says
{
"name": "java-lsp",
"version": "1.0.1",
"description": "Real-time Java code intelligence for Claude — compile errors, go-to-definition, find references, and type info via Eclipse JDT Language Server (jdtls).",
"author": {
"name": "MSApps",
"email": "[email protected]",
"url": "https://msapps.mobi"
},
"homepage": "https://msapps.mobi/plugins",
"repository": "https://github.com/MSApps-Mobile/claude-plugins",
"license": "MIT",
"privacy_policy": "https://opsagents.agency/privacy",
"terms_of_service": "https://opsagents.agency/terms",
"keywords": [
"java",
"jdtls",
"eclipse-jdt",
"android",
"maven",
"gradle",
"spring",
"lsp",
"code-intelligence",
"diagnostics",
"sosa-agents"
],
"lspServers": "./.lsp.json",
"sosa": {
"compliant": true,
"level": 1,
"impact": "low",
"methodology": "https://github.com/MSApps-Mobile/claude-plugins/blob/main/docs/SOSA.md",
"whitepaper": "https://github.com/MSApps-Mobile/claude-plugins/blob/main/docs/sosa-whitepaper.pdf",
"pillars": {
"supervised": "Fully autonomous — read-only code analysis, no external calls or side effects",
"orchestrated": "LSP protocol handles diagnostics, navigation, and hover automatically on file changes",
"secured": "Not sandboxed: build-tool import (Gradle/Maven, which executes project build scripts) and autobuild are OFF by default; enable them only for trusted projects",
"agents": "R=java-code-intelligence, T=jdtls, M=none, P=analyze-on-edit"
}
},
"topics": [
"sosa-agents"
]
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 144 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- today First seen · 46 lines scan A 8e0c13b60b45
java-lsp is a plugin published in the GitHub repository MSApps-Mobile/claude-plugins (10 stars, last pushed today), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-10-18.
Other plugins, from other repositories
jdb-agentic-debugger marketplace
Java debugging tools for AI agents using JDB (Java Debugger CLI).
jdb-debugger
Debug Java applications in real time using JDB (Java Debugger CLI). Attach to running JVMs or launch new ones under JDB, set breakpoints, step through code, inspect variables, analyze threads, and diagnose exceptions.
dejared
Java decompiler and JAR analyzer. Decompile classes, search bytecode, and read resources embedded in JAR, WAR, EAR, and AAR archives.
java-agent-debugger
Debug Java programs interactively from the command line via the jdbg CLI: launch a program or attach to a running JVM (JDWP), set breakpoints, step through code, and inspect variables, expressions, threads, and exceptions. Stateful background sessions with structured (text/JSON) output. Cross-platform, native on…
jdwp-debugging
Java JDWP debugger via MCP — set breakpoints, inspect runtime state, evaluate expressions, mutate variables, catch exceptions at throw site, trace execution with logpoints.
java-code-simplifier
A plugin for simplifying Java and Spring Boot code using established practices for business software.