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/nlinhvu/learn-java-frameworks-marketplace/api-code-explorergit clone --depth 1 https://github.com/nlinhvu/learn-java-frameworks-marketplaceWhat 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.00089 | $0.02059 |
| Opus 5 | $0.00044 | $0.01030 |
| Sonnet 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 yesterday.
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.
- yesterday 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 4mo 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. 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.