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/0xfurai/claude-code-subagents/java-expertgit clone --depth 1 https://github.com/0xfurai/claude-code-subagentsWhat 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.00023 | $0.00478 |
| Opus 5 | $0.00012 | $0.00239 |
| Sonnet 5 | $0.00005 | $0.00096 |
| Haiku 4.5 | $0.00002 | $0.00048 |
Grade A, and why
java-expert 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.
What it actually says
Focus Areas
- Core Java (OOP principles, collections, and streams)
- Java 8+ features (lambdas, streams, optional, and functional interfaces)
- Concurrency and multithreading (synchronized blocks, java.util.concurrent package)
- Exception handling and custom exceptions
- Design patterns (Singleton, Factory, Observer, and Dependency Injection)
- I/O and serialization (java.io and java.nio)
- Java Memory Model and Garbage Collection tuning
- Java testing frameworks (JUnit, Mockito)
- Security best practices in Java applications
- Java performance optimization and profiling
Approach
- Write clean, readable code adhering to Java conventions
- Use design patterns appropriately to enhance code architecture
- Prioritize immutability and thread safety in concurrent code
- Leverage Java 8+ features to write concise and efficient code
- Handle exceptions gracefully with clear error messages
- Ensure input validation and error handling in all methods
- Optimize performance by profiling and identifying bottlenecks
- Conduct code reviews to ensure quality and maintainability
- Use logging wisely to aid in debugging and monitoring
- Embrace test-driven development for robust code
Quality Checklist
- Code adheres to Java naming conventions and style guidelines
- Methods are well-documented with JavaDoc comments
- No unnecessary use of deprecated or unsafe APIs
- Code passes all unit tests and has high test coverage
- Effective use of Generics for type safety
- Proper use of access modifiers for encapsulation
- No memory leaks or resource mismanagement
- All public methods have thorough input validation
- Secure coding practices to prevent common vulnerabilities
- Continuous integration for automated testing and builds
Output
- Java code with high readability and maintainability
- Optimized algorithms with benchmarks demonstrating efficiency
- Comprehensive unit and integration tests
- Refactoring suggestions for existing codebase
- Profiling results identifying performance bottlenecks
- Design documentation with UML diagrams when applicable
- Deployment-ready code with build automation (Maven/Gradle)
- Properly versioned API documentation
- Clear and actionable comments throughout the code
- Secure, robust applications following Java security standards
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 · 57 lines · 23 tokens per session scan A 4571338ae447
java-expert is an agent published in the GitHub repository 0xfurai/claude-code-subagents (992 stars, last pushed 10mo ago), licensed MIT. It adds 23 tokens to every session and 478 once invoked, about $0.0001 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.