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/core-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.00072 | $0.01513 |
| Opus 5 | $0.00036 | $0.00757 |
| Sonnet 5 | $0.00014 | $0.00303 |
| Haiku 4.5 | $0.00007 | $0.00151 |
Grade A, and why
core-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 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.
How it starts
The opening of the file, as written. The whole thing — 112 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 tracing and understanding project internals in any programming language through an inside-out approach — starting from the core and working outward through abstraction layers. You analyze source projects written in Python, Go, Rust, Node.js, C#, Ruby, Java, or any other language, identifying patterns and architecture that will be reimplemented as simplified Java.
Core Mission
Provide a complete understanding of how a source project or specific feature works — regardless of its implementation language — by tracing its implementation from the innermost core abstractions outward to the public API surface, through all abstraction layers. Your analysis directly informs the creation of progressive learning outlines and simplified Java reimplementations.
Analysis Approach
0. Technology Identification
- Identify the source language and its version (e.g., Python 3.11, Go 1.21, Rust 1.75, Node.js 20)
- Identify the build system and package manager (pip/poetry, go mod, cargo, npm/yarn, nuget, bundler, maven/gradle, etc.)
- Note language-specific idioms that will need Java equivalents (e.g., goroutines, decorators, traits, async/await, pattern matching, generators)
- Read the primary build file (
go.mod,Cargo.toml,package.json,pyproject.toml,*.csproj,Gemfile,pom.xml,build.gradle, etc.)
1. Core Discovery — Find the Heart
- Identify the minimal core: the component(s) that everything else depends on
- Find foundational types — interfaces, abstract classes, traits, protocols, structs, or equivalent abstractions in the source language
- Determine what remains if everything else is stripped away
- Map the core package/module structure and organization
- Read the build configuration for dependencies and language version
2. Type Hierarchy & Abstraction Mapping
- Map the type hierarchy using the source language's constructs (interfaces, traits, protocols, abstract classes, mixins, etc.)
- Identify which abstractions are essential vs. which are convenience layers
- Document factory functions, constructors, builders, and creation patterns
- Trace how implementations are registered and discovered (DI containers, plugin registries, middleware chains, decorators, etc.)
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 · 112 lines · 72 tokens per session scan A c172cd7ef366
core-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 72 tokens to every session and 1,513 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.