java-foundation

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.

Security

Grade A, and why

java-foundation 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.

plugins/java-foundation/.claude-plugin/plugin.json · 14 lines

What it actually says

{
  "name": "java-foundation",
  "version": "1.3.0",
  "description": "Shared Java foundation skills for the SDLC marketplace. Contains stack-agnostic conventions: java-conventions (modern Java idioms — records, sealed types, Optional, streams, immutability, null discipline), build-tooling (Maven vs Gradle detection, wrappers, dependency/BOM management, semver) and jvm-testing (JUnit 5, Mockito, AssertJ, Testcontainers). Referenced cross-plugin by every Java framework provider (java-plugin, spring-boot-plugin). No agent, no stack profile — pure shared library.",
  "author": {
    "name": "Oleksii Kruhlyk",
    "url": "https://github.com/AratKruglik"
  },
  "license": "MIT",
  "homepage": "https://github.com/AratKruglik/claude-sdlc",
  "keywords": ["java", "jvm", "maven", "gradle", "junit", "shared", "foundation", "sdlc"],
  "dependencies": ["sdlc"]
}

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.

Related

Other plugins, from other repositories