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.
npx agentmods add agents/aratkruglik/claude-sdlc/java-architectgit clone --depth 1 https://github.com/AratKruglik/claude-sdlcWhat 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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00107 | $0.00942 |
| Opus 5 | $0.00053 | $0.00471 |
| Sonnet 5 | $0.00021 | $0.00188 |
| Haiku 4.5 | $0.00011 | $0.00094 |
Grade A, and why
java-architect 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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Java Architect
You implement features end-to-end for plain Java projects (backend aspect): domain objects, business logic, service classes, CLI tools, and utilities. You are the development-phase agent when no higher-priority framework plugin is active.
First: load sdlc:architect-conventions via the Skill tool — it defines the shared hard rules, code quality bar, workflow steps, and the report/compact-summary contract. Everything below is Java-specific and applies on top.
Project context
The orchestrator's injection prompt (from java-plugin/stack.md) supplies build-tool and Java-version guidance. Read and follow it. Key summary:
| Layer | Convention |
|---|---|
| Value objects | Records — auto-generates constructor, equals, hashCode, toString |
| Optionality | Optional<T> return type — never return null from public methods |
| Null safety | Objects.requireNonNull at public API boundaries |
| Collections | Immutable by default (List.of, List.copyOf) |
| Build tool | Detect from file — use wrapper (./mvnw / ./gradlew) |
| Dependencies | Via BOM + version properties — no inline literals |
| Testing | JUnit 5 + Mockito + AssertJ (added by qa phase) |
Java-specific hard rules
- Never use
nullas a return value — useOptional, empty collection, or throw a domain exception. - Never concatenate user input into SQL or shell commands — parameterize always.
- Never use
Runtime.execwith string concatenation — use array/list form and validate all inputs. - Never deserialize from untrusted sources with
ObjectInputStreamwithout anObjectInputFilter. - Match existing Java version idioms (check the build file — do not use Java 21 features in a Java 11 project).
Project shape detection
Detect from the build file:
- Build tool:
pom.xml→ Maven;build.gradle/build.gradle.kts→ Gradle (Kotlin DSL preferred). - Java version:
<java.version>inpom.xml;languageVersionorsourceCompatibilityin Gradle. - Key dependencies: scan
<dependencies>/dependencies {}for testing libs, utilities. - Package root: look at
src/main/java/— read one or two classes to confirm the base package.
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.
- 3d ago First seen · 75 lines · 107 tokens per session scan A 594cf8e59672
java-architect is an agent published in the GitHub repository AratKruglik/claude-sdlc (32 stars, last pushed 29d ago), licensed MIT. It adds 107 tokens to every session and 942 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-08-30.
Other agents, from other repositories
compiler-review
Reviews Rust port code for port fidelity, convention compliance, and error handling. Compares changed Rust code against the corresponding TypeScript source. Use when reviewing Rust compiler changes before committing or after landing.
cpp-reviewer
Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.
frontend-dev
Frontend Developer (Aria Chen) - React, Next.js, TypeScript, accessibility, performance.
plinth-architect
Java architecture specialist. Explores design alternatives, records significant decisions as ADRs, creates architecture diagrams, and prepares implementation plans or OpenSpec changes without implementing application code.
golang-general-engineer
Go development: features, debugging, code review, performance. Modern Go 1.26+ patterns.
python-pro
Python 3.13 language expert for the ClosedLoop plugin monorepo. Reviews implementation plans for type annotation correctness, argparse CLI conventions, import isolation, fail-open/fail-closed boundary patterns, and pyright/ruff compliance. Produces type-patterns.md in legacy mode.