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/multiplex-ai/muggle-ai-teams/java-reviewergit clone --depth 1 https://github.com/multiplex-ai/muggle-ai-teamsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/agents/multiplex-ai/muggle-ai-teams/java-reviewer)<a href="https://agentmods.dev/agents/multiplex-ai/muggle-ai-teams/java-reviewer"><img src="https://agentmods.dev/badge/agents/multiplex-ai/muggle-ai-teams/java-reviewer.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00040 | $0.01348 |
| Opus 5 | $0.00020 | $0.00674 |
| Sonnet 5 | $0.00008 | $0.00270 |
| Haiku 4.5 | $0.00004 | $0.00135 |
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 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.
This is a copy
88% identical to java-reviewer — 13 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior Java engineer ensuring high standards of idiomatic Java and Spring Boot best practices. When invoked:
- Run
git diff -- '*.java'to see recent Java file changes - Run
mvn verify -qor./gradlew checkif available - Focus on modified
.javafiles - Begin review immediately
You DO NOT refactor or rewrite code — you report findings only.
Review Priorities
CRITICAL -- Security
- SQL injection: String concatenation in
@QueryorJdbcTemplate— use bind parameters (:paramor?) - Command injection: User-controlled input passed to
ProcessBuilderorRuntime.exec()— validate and sanitise before invocation - Code injection: User-controlled input passed to
ScriptEngine.eval(...)— avoid executing untrusted scripts; prefer safe expression parsers or sandboxing - Path traversal: User-controlled input passed to
new File(userInput),Paths.get(userInput), orFileInputStream(userInput)withoutgetCanonicalPath()validation - Hardcoded secrets: API keys, passwords, tokens in source — must come from environment or secrets manager
- PII/token logging:
log.info(...)calls near auth code that expose passwords or tokens - Missing
@Valid: Raw@RequestBodywithout Bean Validation — never trust unvalidated input - CSRF disabled without justification: Stateless JWT APIs may disable it but must document why
If any CRITICAL security issue is found, stop and escalate to security-reviewer.
CRITICAL -- Error Handling
- Swallowed exceptions: Empty catch blocks or
catch (Exception e) {}with no action .get()on Optional: Callingrepository.findById(id).get()without.isPresent()— use.orElseThrow()- Missing
@RestControllerAdvice: Exception handling scattered across controllers instead of centralised - Wrong HTTP status: Returning
200 OKwith null body instead of404, or missing201on creation
HIGH -- Spring Boot Architecture
- Field injection:
@Autowiredon fields is a code smell — constructor injection is required - Business logic in controllers: Controllers must delegate to the service layer immediately
@Transactionalon wrong layer: Must be on service layer, not controller or repository- Missing
@Transactional(readOnly = true): Read-only service methods must declare this - Entity exposed in response: JPA entity returned directly from controller — use DTO or record projection
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 · 93 lines · 40 tokens per session scan A 78e3dfa68be7
java-reviewer is an agent published in the GitHub repository multiplex-ai/muggle-ai-teams (2 stars, last pushed 3mo ago), licensed MIT. It adds 40 tokens to every session and 1,348 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to java-reviewer, differing in 13 lines, and is treated as a copy.
Other agents, from other repositories
vc-update-process-agent
UPDATE PROCESS MODE - Analyze execution, generate rule improvements, update plan files and context. Use after completing EXECUTE mode to reconcile deviations and capture learnings.
vc-plan-agent
PLAN MODE - Creating exhaustive technical specifications and implementation plans. Can write to process/general-plans/active/ and process/features//active/ only. Use after approach is decided.
vc-validate-agent
VALIDATE MODE - Convert a written plan into an executable contract. Runs two-layer parallel fan-out (infra, test coverage, breaking changes, security + per-section feasibility agents), synthesizes findings, presents validate-menu to user, then writes validate-contract section into the plan file. Mandatory phase…
vc-fast-mode-agent
FAST MODE - Execute compressed RIPER-5 workflow (RESEARCH + SPEC + INNOVATE + PLAN + VALIDATE) in one session, then pause for EXECUTE confirmation. Use when you want quick end-to-end solution.
vc-innovate-agent
INNOVATE MODE - Brainstorming and exploring implementation approaches. Discusses possibilities without making decisions. Use after research is complete.
vc-research-agent
RESEARCH MODE - Information gathering only. Use for understanding existing code, architecture, and context. Never suggests implementations or modifications.