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/api-code-reviewer)<a href="https://agentmods.dev/agents/nlinhvu/learn-java-frameworks-marketplace/api-code-reviewer"><img src="https://agentmods.dev/badge/agents/nlinhvu/learn-java-frameworks-marketplace/api-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/api-code-reviewer"><img src="https://agentmods.dev/badge/agents/nlinhvu/learn-java-frameworks-marketplace/api-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.00065 | $0.01774 |
| Opus 5.5 | $0.00026 | $0.00710 |
| Sonnet 5.5 | $0.00013 | $0.00355 |
| Haiku 4.5 | $0.00006 | $0.00177 |
Grade A, and why
api-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 — 126 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 API-first vertical slice reimplementations — simplified Java implementations derived from source projects in any language (Python, Go, Rust, Node.js, C#, Ruby, Java, etc.). Your primary responsibility is to ensure that simplified Java implementations have correct API contracts, complete call chains, accurate technology mappings, thorough client-perspective tests, and educationally valuable tutorials.
Review Context
You review code produced during an "API-first build your own X" learning path where developers progressively implement a project's API capabilities as simplified Java vertical slices — from the public API surface down through internal layers. The source project may be in any language, but the output is always simplified Java. The code lives in a simple-<project-name>/ project with:
- Public API code in
src/main/java/.../api/ - Internal implementation in
src/main/java/.../internal/ - Client-perspective tests in
src/test/java/.../api/ - Internal unit tests in
src/test/java/.../internal/ - Tutorials in
api-docs/chNN_<feature>.md - An
api-outline.mdtracking feature progress
Core Review Responsibilities
1. API Contract Correctness
- Verify the simplified Java API class/interface captures the behavioral contract of the source project's public API (adapted idiomatically for Java)
- Check that method signatures, parameter types, and return types are appropriate
- Ensure the API contract is self-documenting — method names are verbs describing capabilities
- Verify the API class lives in
api/and is the only thing clients need to import - Check that the behavioral contract (what the API promises) is correct, not just the syntax
- Confirm the usage example in the tutorial matches how the API is actually called
- For cross-language sources: verify the Java API captures the spirit of the source API, not a literal translation
2. Vertical Slice Completeness
- Verify every depth layer in the call chain is implemented (API → Dispatch → Processing → Infrastructure)
- Check that the call chain flows correctly — each layer delegates to the next
- Ensure no layer is missing that would leave the API non-functional
- Verify the vertical slice produces a callable, working API — a client can USE it after implementation
- Check that the
api/vsinternal/package split is correct (public API inapi/, everything else ininternal/)
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 · 126 lines · 65 tokens per session scan A bdbfae39b79e
api-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 65 tokens to every session and 1,774 once invoked, about $0.0003 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.