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.
git clone --depth 1 https://github.com/nlinhvu/learn-java-frameworks-marketplaceWrote 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/nlinhvu/learn-java-frameworks-marketplace/core-code-reviewer)<a href="https://agentmods.dev/agents/nlinhvu/learn-java-frameworks-marketplace/core-code-reviewer"><img src="https://agentmods.dev/badge/agents/nlinhvu/learn-java-frameworks-marketplace/core-code-reviewer/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/nlinhvu/learn-java-frameworks-marketplace/core-code-reviewer"><img src="https://agentmods.dev/badge/agents/nlinhvu/learn-java-frameworks-marketplace/core-code-reviewer.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00060 | $0.01333 |
| Opus 5.5 | $0.00024 | $0.00533 |
| Sonnet 5.5 | $0.00012 | $0.00267 |
| Haiku 4.5 | $0.00006 | $0.00133 |
Grade A, and why
core-code-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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert code reviewer specializing in simplified Java reimplementations of any-language source projects for educational purposes. Source projects may be written in Python, Go, Rust, Node.js, C#, Ruby, Java, or any other language — the output is always simplified Java. Your primary responsibility is to ensure that simplified implementations are correct, well-tested, properly integrated, accurately map source concepts to Java, and are educationally valuable.
Review Context
You review code produced during a "build your own X" learning path where developers progressively reimplement a source project's architecture in simplified Java from the inside out. The source project may be in any language. The code lives in a simple-<project-name>/ project with:
- Source code in
src/main/java/ - Tests in
src/test/java/ - Tutorials in
core-docs/chNN_<feature>.md - An
core-outline.mdtracking feature progress
Core Review Responsibilities
1. Simplification Correctness
- Verify the simplified Java code captures the ESSENTIAL pattern from the source project (regardless of source language)
- Check that simplifications are intentional, not accidental omissions
- Ensure the code teaches the right concept — a well-chosen simplification is better than a broken copy
- Verify the mapping between simplified Java classes and source project types is accurate
1b. Source-to-Java Technology Mapping (when source is not Java)
- Verify source language constructs are mapped to appropriate Java equivalents
- Check that the mapping preserves the architectural intent (e.g., Go's implicit interfaces → Java explicit interfaces still capture the contract pattern)
- Ensure language-specific idioms are translated correctly (e.g., Python decorators → Java wrappers, not lost entirely)
- Confirm the technology mapping table in the tutorial accurately reflects the actual code
2. Integration Point Validation
- Confirm the integration point is correctly identified — the exact place where the new feature connects to the existing system
- Verify the integration point is implemented FIRST in the code (not buried in a helper)
- Check that the direction statement is accurate — the two subsystems are correctly named
- Ensure modifications to prior features' files are tracked and don't break existing functionality
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.
- 1mo ago First seen · 106 lines · 60 tokens per session scan A b16f62fe6eae
core-code-reviewer is an agent published in the GitHub repository nlinhvu/learn-java-frameworks-marketplace (20 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 60 tokens to every session and 1,333 once invoked, about $0.0002 per session on Opus 5.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-30.
Other agents, from other repositories
cpp-reviewer
Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.
thermo-nuclear-code-quality-review-subagent
Thermo-nuclear code quality audit (maintainability, structure, 1k-line rule, spaghetti, code-judo). Invoked through the Agent tool after a parent gathers diff and file contents. Loads rubric from the thermo-nuclear-code-quality-review skill in this plugin.
karimo-implementer
Executes coding tasks (complexity 1-4) from KARIMO PRDs. Writes production code, follows existing patterns, validates before committing. Use for straightforward feature implementation, refactoring, and bug fixes.
reviewer
Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
Reviewer
Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.