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/sifxprime/kodelyth-ecc/java-reviewergit clone --depth 1 https://github.com/sifxprime/kodelyth-eccWhat 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 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
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.
- 2d ago First seen · 93 lines · 40 tokens per session scan A 78e3dfa68be7
java-reviewer is an agent published in the GitHub repository sifxprime/kodelyth-ecc (11 stars, last pushed 11d 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
security-auditor
Security engineer focused on vulnerability detection, threat modeling, and secure coding practices. Use for security-focused code review, threat analysis, or hardening recommendations.
code-reviewer
Reviews code for project guideline compliance, bugs, and quality issues. Use after writing code, before commits, or before PRs. Specify files to review or defaults to unstaged git changes. High-confidence issues only (80+) to minimize noise.
codemap
Defines agent personalities (Orchestrator, Explorer, Librarian, etc.) and manages their configuration lifecycle. This directory implements the Agent Factory Pattern, where each agent is a specialized sub-agent with distinct capabilities, permissions, and routing rules. The Orchestrator agent (src/agents/index.ts)…
design-reviewer
Design lead + expert design critic. Two modes: Mode A — authors the project's root DESIGN.md (design identity) at project start. Mode B — reviews built UI against DESIGN.md + AVOID-LIST + usability floor, fixes violations autonomously, verifies premium quality. Delegate when: a UI project has no DESIGN.md yet, UI…
qa-sentinel
The QA Sentinel designs test strategy -- what kinds of tests, where, why, and how they compose into a quality system that actually catches bugs. It does not write tests (that is the Testing agent). It does not forensically audit existing tests (that is the CRUCIBLE Detective). It is the architect of quality -- the…
conversation-analyzer
Use this agent when analyzing conversation transcripts to find behaviors worth preventing with hooks. Triggered by /egc-hookify without arguments.