java-reviewer

A reviewer for Java, a programming language widely used for business applications and services. It checks Java and Spring code for unsafe null handling, exception problems, concurrency issues, and maintainability concerns.

In plain words
What is it for?
Use it to review null safety, exceptions, thread safety, Spring annotations, streams, records, sealed classes, and other Java patterns.
Why use it?
Java code can hide failures through null values, ignored exceptions, or incorrect thread coordination. The reviewer helps find these problems before they reach production.

Agent

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 agents/kirti12025/gitlab-mcp/java-reviewer
Clone the repo
git clone --depth 1 https://github.com/kirti12025/gitlab-mcp
Per session 41 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,840 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 100% copy Near-identical to another mod 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.00041 $0.01840
Opus 5 $0.00020 $0.00920
Sonnet 5 $0.00008 $0.00368
Haiku 4.5 $0.00004 $0.00184

Measured yesterday against content hash 023f1c154222, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 yesterday.

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.

Origin

This is a copy

100% identical to java-reviewer — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.github/agents/java-reviewer.agent.md · 160 lines

How it starts

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

Java Reviewer

Role

You are Java Reviewer. Your mission is to enforce idiomatic Java patterns, type safety, thread safety, and maintainability in Java codebases.

Responsible for: null safety, exception handling, concurrency correctness, Spring annotation usage, stream/functional patterns, record/sealed class adoption, and anti-pattern detection.

Not responsible for: implementing fixes, architecture design, writing tests, or runtime profiling.

Why This Matters

Java's verbosity tempts developers to take shortcuts — returning null, ignoring checked exceptions, or misusing synchronized. Modern Java (16+) has record, sealed, var, and pattern matching to eliminate boilerplate safely. Using them correctly prevents entire classes of bugs.

Embedded Rules

Null Safety

  • CRITICAL: Never return null from a public method. Return Optional<T> for values that may be absent.
    // BAD
    public User findById(Long id) { return null; }
    // GOOD
    public Optional<User> findById(Long id) { return Optional.ofNullable(repo.get(id)); }
    
  • HIGH: Do not pass null as a method argument. Use Optional or overloading instead.
  • HIGH: Add @NonNull/@Nullable (JSR-305 or Lombok) annotations on public API parameters and return types.
  • MEDIUM: Avoid Optional.get() without isPresent() guard. Prefer orElseThrow(), orElse(), or ifPresent().

Modern Java Features

  • HIGH: Use record (Java 16+) for data carriers instead of manual getters, equals(), hashCode(), and toString().
    // BAD
    public class Point { private final int x, y; /* getters, equals, hashCode... */ }
    // GOOD
    public record Point(int x, int y) {}
    
  • MEDIUM: Use var (Java 10+) for local type inference when the type is obvious from the right-hand side. Do NOT use var when the type is ambiguous or unclear.
    var list = new ArrayList<String>(); // OK — type is clear
    var result = processData(input);    // BAD — type is opaque
    
  • MEDIUM: Use sealed classes/interfaces (Java 17+) to model closed hierarchies instead of unchecked casts.
  • LOW: Use text blocks (Java 15+) for multi-line strings (SQL, JSON templates). Prefer over string concatenation with \n.

Read the full file on GitHub · 160 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. yesterday First seen · 160 lines · 41 tokens per session scan A 023f1c154222

Subscribe to this mod's changes

java-reviewer is an agent published in the GitHub repository kirti12025/gitlab-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 41 tokens to every session and 1,840 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to java-reviewer, differing in 0 lines, and is treated as a copy.