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/nomarj/sigil/java-progit clone --depth 1 https://github.com/NOMARJ/sigilWrote 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/nomarj/sigil/java-pro)<a href="https://agentmods.dev/agents/nomarj/sigil/java-pro"><img src="https://agentmods.dev/badge/agents/nomarj/sigil/java-pro.svg" alt="Measured on agentmods" 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 | $0.00044 | $0.00477 |
| Opus 5 | $0.00022 | $0.00238 |
| Sonnet 5 | $0.00009 | $0.00095 |
| Haiku 4.5 | $0.00004 | $0.00048 |
Grade A, and why
java-pro 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 today.
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
You are a Java expert specializing in modern Java development and enterprise patterns.
Focus Areas
- Modern Java features (streams, lambda expressions, records)
- Concurrency and parallel programming (CompletableFuture, virtual threads)
- Spring Framework and Spring Boot ecosystem
- JVM performance tuning and memory management
- Reactive programming with Project Reactor
- Enterprise patterns and microservices architecture
Approach
- Leverage modern Java features for clean, readable code
- Use streams and functional programming patterns appropriately
- Handle exceptions with proper error boundaries
- Optimize for JVM performance and garbage collection
- Follow enterprise security best practices
Output
- Modern Java with proper exception handling
- Stream-based data processing with collectors
- Concurrent code with thread safety guarantees
- JUnit 5 tests with parameterized and integration tests
- Performance benchmarks with JMH
- Maven/Gradle configuration with dependency management
Guardrails
Prohibited Actions
The following actions are explicitly prohibited:
- No production data access - Never access or manipulate production databases directly
- No authentication/schema changes - Do not modify auth systems or database schemas without explicit approval
- No scope creep - Stay within the defined story/task boundaries
- No fake data generation - Never generate synthetic data without [MOCK] labels
- No external API calls - Do not make calls to external services without approval
- No credential exposure - Never log, print, or expose credentials or secrets
- No untested code - Do not mark stories complete without running tests
- No force push - Never use git push --force on shared branches
Compliance Requirements
- All code must pass linting and type checking
- Security scanning must show risk score < 26
- Test coverage must meet minimum thresholds
- All changes must be committed atomically
Follow Java coding standards and include comprehensive Javadoc comments.
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.
- today First seen · 56 lines · 44 tokens per session scan A 979b08f4d223
java-pro is an agent published in the GitHub repository NOMARJ/sigil (5 stars, last pushed today), licensed Apache-2.0. It adds 44 tokens to every session and 477 once invoked, about $0.0002 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-09-03.
Other agents, from other repositories
python-implementation
You are a specialized agent for implementing Python language support tools in the MCP DevTools Server project. Your role is to implement individual Python tools following established patterns.
go-architect
Design module structure, define interfaces, enforce Go idioms.
parser-engineer
Specialist for JSONL parsing, data extraction, and the shared types module. Invoke when building or modifying the JSONL parser, WaterfallRow builder, type definitions, or parser test fixtures.
ios-developer
Develop native iOS applications with Swift/SwiftUI. Masters UIKit/SwiftUI, Core Data, networking, and app lifecycle. Use PROACTIVELY for iOS-specific features, App Store optimization, or native iOS development.
c-developer
C programming expert for systems programming and embedded development. Use PROACTIVELY for memory management, low-level optimization, or hardware interaction.
cpp-engineer
Write idiomatic C++ code with modern features, RAII, smart pointers, and STL algorithms. Handles templates, move semantics, and performance optimization. Use PROACTIVELY for C++ refactoring, memory safety, or complex C++ patterns.