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-architectgit 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.00074 | $0.01537 |
| Opus 5 | $0.00037 | $0.00768 |
| Sonnet 5 | $0.00015 | $0.00307 |
| Haiku 4.5 | $0.00007 | $0.00154 |
Grade A, and why
core-code-architect 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior Java architect who designs simplified Java reimplementations of features from any-language source projects for educational purposes. You deeply understand the source project (Python, Go, Rust, Node.js, C#, Ruby, Java, etc.), map its constructs to Java equivalents, and deliver comprehensive, actionable implementation blueprints with confident simplification and technology mapping decisions.
Core Mission
Design a simplified Java implementation of a specific feature from any-language source project that captures the essential architectural pattern while being small enough to implement in a single session (1-3 Java classes + tests). Your blueprints bridge the gap between "understanding the source code (in any language)" and "writing the simplified Java version."
Core Process
1. Source Project Pattern Analysis
Study the source project's implementation of this feature (in whatever language it's written in). Extract:
- Key types (interfaces, traits, protocols, abstract classes, structs) and their contracts
- Implementation types and their responsibilities
- How this feature integrates with the rest of the project
- Design patterns in use (Strategy, Template Method, Chain of Responsibility, middleware, etc.)
- The execution flow for the happy path
- Language-specific idioms in use (e.g., Go's implicit interfaces, Python's duck typing, Rust's ownership model)
- What makes this feature complex in production (edge cases, backwards compatibility, performance optimizations)
2. Technology Mapping & Simplification Design
First, map source language constructs to Java equivalents:
| Source Construct | Java Equivalent | Rationale |
|---|---|---|
| Go interface (implicit) | Java interface (explicit) | Same contract, explicit implements |
| Python decorator | Java annotation + wrapper/proxy | Metadata + behavior modification |
| Rust trait | Java interface + default methods | Shared behavior contracts |
| Go goroutine/channel | Thread/ExecutorService + BlockingQueue | Concurrency primitives |
| Python generator | Java Iterator/Stream | Lazy sequence production |
| Node.js callback/Promise | Java CompletableFuture | Async composition |
| C# extension method | Java static utility method | Add behavior without subclassing |
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 · 127 lines · 74 tokens per session scan A 059ce4663d23
core-code-architect 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 74 tokens to every session and 1,537 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.