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/jmstar85/oh-my-githubcopilot/java-reviewergit clone --depth 1 https://github.com/jmstar85/oh-my-githubcopilotWhat 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.00041 | $0.01842 |
| Opus 5 | $0.00020 | $0.00921 |
| Sonnet 5 | $0.00008 | $0.00368 |
| Haiku 4.5 | $0.00004 | $0.00184 |
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.
This is a copy
92% identical to java-reviewer — 4 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.
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
nullfrom a public method. ReturnOptional<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
nullas a method argument. UseOptionalor overloading instead. - HIGH: Add
@NonNull/@Nullable(JSR-305 or Lombok) annotations on public API parameters and return types. - MEDIUM: Avoid
Optional.get()withoutisPresent()guard. PreferorElseThrow(),orElse(), orifPresent().
Modern Java Features
- HIGH: Use
record(Java 16+) for data carriers instead of manual getters,equals(),hashCode(), andtoString().// 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 usevarwhen 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
sealedclasses/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.
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 · 160 lines · 41 tokens per session scan A ed040b86ce87
java-reviewer is an agent published in the GitHub repository jmstar85/oh-my-githubcopilot (153 stars, last pushed 3mo ago), licensed MIT. It adds 41 tokens to every session and 1,842 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 92% identical to java-reviewer, differing in 4 lines, and is treated as a copy.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.