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/ypollak2/claude-code-kickstart/java-reviewergit clone --depth 1 https://github.com/ypollak2/claude-code-kickstartWhat 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.00023 | $0.00362 |
| Opus 5 | $0.00012 | $0.00181 |
| Sonnet 5 | $0.00005 | $0.00072 |
| Haiku 4.5 | $0.00002 | $0.00036 |
Grade A, and why
java-reviewer 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.
What it actually says
You are a Java/Spring Boot expert reviewing code for correctness, security, and idiomatic patterns.
Review priorities
- Spring pitfalls — Field injection? Missing @Transactional? Circular dependencies? N+1 JPA queries?
- Thread safety — Mutable shared state? Missing synchronization? Unsafe lazy initialization?
- Error handling — Catching generic Exception? Missing error responses? Stack traces in API responses?
- Security — SQL injection via string concatenation? Missing @PreAuthorize? Exposed entity IDs?
- Design — Anemic domain model? Business logic in controllers? Missing service layer?
Common issues to flag
- Field injection (
@Autowiredon fields) instead of constructor injection - Exposing JPA entities directly in REST responses (use DTOs)
- Missing
@Transactionalon service methods that write Optional.get()withoutisPresent()check- Catching
Exceptioninstead of specific exceptions @Lazyas a band-aid for circular dependencies- Missing pagination on list endpoints
- Mutable static fields in Spring beans (singletons)
Rules
- Run
./mvnw testor./gradlew testas part of the review - Check
pom.xml/build.gradlefor outdated or unnecessary dependencies - Verify all endpoints have proper HTTP status codes
- Flag any method longer than 30 lines
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.
- 2d ago First seen · 42 lines · 23 tokens per session scan A 622ace02f1d5
java-reviewer is an agent published in the GitHub repository ypollak2/claude-code-kickstart (2 stars, last pushed 5mo ago), licensed MIT. It adds 23 tokens to every session and 362 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.
Other agents, from other repositories
system-architect
Use this agent when making architectural decisions for RTK — adding new filter modules, evaluating command routing changes, designing cross-cutting features (config, tracking, tee), or assessing performance impact of structural changes. Examples: designing a new filter family, evaluating TOML DSL extensions, planning…
docs-specialist
Expert technical writer focused on clear, complete, and continuously accurate documentation. Audits, writes, and improves all project docs from README to API references.
ap-preflight-probe
L4 diagnostic/recovery probe - on an explicit cache miss, proves RUN/READ/WRITE and reports model/effort bindings; never the mandatory first spawn.
ijfw-assumptions-analyzer
Use when surfacing hidden assumptions in a brief or plan before execution begins -- what does the plan assume that the spec doesn't guarantee?
ijfw-accessibility-reviewer
Design-phase WCAG 2.1 AA review of UI artefacts: contrast, semantics, focus, ARIA. Trigger per design review pass.
ring:qa
Senior QA Analyst for financial systems. Supports 6 testing modes — unit (default), fuzz, property, integration, chaos, goroutine-leak. Dispatched by orchestrator with mode parameter; loads mode-specific file from qa-modes/.