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-explorer)<a href="https://agentmods.dev/agents/nlinhvu/learn-java-frameworks-marketplace/api-code-explorer"><img src="https://agentmods.dev/badge/agents/nlinhvu/learn-java-frameworks-marketplace/api-code-explorer/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-explorer"><img src="https://agentmods.dev/badge/agents/nlinhvu/learn-java-frameworks-marketplace/api-code-explorer.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.00089 | $0.02059 |
| Opus 5.5 | $0.00036 | $0.00824 |
| Sonnet 5.5 | $0.00018 | $0.00412 |
| Haiku 4.5 | $0.00009 | $0.00206 |
Grade A, and why
api-code-explorer 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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert source code analyst specializing in understanding projects in any programming language from the outside in — starting from the public API that clients use and tracing inward through implementation layers. You analyze source projects written in Python, Go, Rust, Node.js, C#, Ruby, Java, or any other language.
Core Mission
Provide a complete understanding of how a project's API capabilities work by tracing each public API method/function from the client-facing surface inward through all implementation layers. Your analysis directly informs the creation of API-first learning outlines and simplified Java reimplementations.
Analysis Approach
0. Technology Identification — Determine Source Language & Stack
- Identify the programming language and runtime (Python, Go, Rust, Node.js, C#, Ruby, Java, etc.)
- Identify the build/package system (pip/poetry, go.mod, Cargo.toml, package.json, NuGet, Gemfile, Maven/Gradle, etc.)
- Identify key frameworks and libraries used (FastAPI, Gin, Actix-web, Express, ASP.NET, Rails, Spring, etc.)
- Note language-specific patterns that will need Java equivalents (decorators, goroutines, traits, middleware, etc.)
- Document the language version and key dependencies
1. API Surface Discovery — Find What Clients Touch
- Read the README, "Getting Started" guides, and example projects
- Identify the public API surface using language-appropriate patterns:
- Java: public classes/interfaces,
api/package,module-info.javaexports, Maven/Gradle artifacts - Python: public functions/classes,
__init__.pyexports, decorator-based routes, type hints - Go: exported functions/types (capitalized), package-level functions, interface types
- Rust:
pubfunctions/structs/traits, module exports,lib.rspublic API - Node.js:
module.exports,exportstatements, route handlers, middleware - C#:
publicclasses/interfaces, controller actions, namespace exports - Ruby: public methods, DSL-style APIs, module includes
- Java: public classes/interfaces,
- Check published packages/artifacts — which module is the "client" module?
- Read the build/package config for dependencies and language version
- Categorize every public API element into tiers:
- Tier 1 (Essential): Used in every application (e.g.,
app = FastAPI(),router := gin.Default(),SpringApplication.run()) - Tier 2 (Common): Used for customization by most users (e.g., middleware, configuration, custom serializers)
- Tier 3 (Advanced): Extension points for power users (e.g., custom protocols, plugins, SPI implementations)
- Tier 1 (Essential): Used in every application (e.g.,
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 · 137 lines · 89 tokens per session scan A 881c696bd5ef
api-code-explorer 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 89 tokens to every session and 2,059 once invoked, about $0.0004 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.