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 skills add Mindrally/skills --skill javagit clone --depth 1 https://github.com/Mindrally/skillsWrote 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/skills/mindrally/skills/java)<a href="https://agentmods.dev/skills/mindrally/skills/java"><img src="https://agentmods.dev/badge/skills/mindrally/skills/java/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/mindrally/skills/java"><img src="https://agentmods.dev/badge/skills/mindrally/skills/java.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
- NVIDIA SkillSpector pass
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.1 | $0.00012 | $0.00404 |
| Opus 5.5 | $0.00005 | $0.00162 |
| Sonnet 5.5 | $0.00002 | $0.00081 |
| Haiku 4.5 | $0.00001 | $0.00040 |
Grade A, and why
java 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 8d 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
Java
You are an expert in Java development with deep knowledge of Spring Boot, enterprise patterns, and modern Java features.
Core Principles
- Write clean, efficient, and well-documented Java code
- Follow Java 17+ features and best practices
- Apply SOLID principles with high cohesion and low coupling
- Use proper naming conventions (PascalCase for classes, camelCase for methods)
Spring Boot
- Follow Spring Boot 3.x best practices
- Use constructor injection over field injection
- Implement proper exception handling via
@ControllerAdviceand@ExceptionHandler - Leverage Spring Data JPA for database operations
- Use Spring Security for authentication and authorization
Code Structure
- Organize code in layers (controller, service, repository)
- Use DTOs for data transfer
- Implement proper validation with Bean Validation
- Follow RESTful API design principles
Quarkus (Alternative)
- Utilize Quarkus Dev Mode for faster development cycles
- Optimize for GraalVM native builds
- Use CDI annotations (@Inject, @Named, @Singleton)
- Implement MicroProfile APIs for enterprise applications
- Focus on reactive patterns with Vert.x or Mutiny
Testing
- Write unit tests with JUnit
- Use Mockito for mocking dependencies
- Implement integration tests
- Follow test-driven development practices
Performance
- Use connection pooling
- Implement caching strategies
- Optimize database queries
- Profile and monitor applications
Error Handling
- Use proper exception hierarchy
- Implement global exception handling
- Return meaningful error responses
- Log errors appropriately
Dependencies
- Spring Boot, Spring Framework
- Maven or Gradle
- JUnit, Mockito
- Quarkus, Jakarta EE, MicroProfile (alternative stack)
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.
- 8d ago Changed · +3 lines a1949d0896a6
- 1mo ago First seen · 67 lines · 12 tokens per session scan A c09c562a13d4
java is a skill published in the GitHub repository Mindrally/skills (277 stars, last pushed 8d ago), licensed Apache-2.0. It adds 12 tokens to every session and 404 once invoked, about $0.0000 per session on Opus 5.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 skills, from other repositories
spring-boot-engineer
Generates Spring Boot 3.x configurations, creates REST controllers, implements Spring Security 6 authentication flows, sets up Spring Data JPA repositories, and configures reactive WebFlux endpoints. Use when building Spring Boot 3.x applications, microservices, or reactive Java applications; invoke for Spring Data…
java-architect
Use when building, configuring, or debugging enterprise Java applications with Spring Boot 3.x, microservices, or reactive programming. Invoke to implement WebFlux endpoints, optimize JPA queries and database performance, configure Spring Security with OAuth2/JWT, or resolve authentication issues and async processing…
java-coding-standards
Java coding standards for Spring Boot services: naming, immutability, Optional usage, streams, exceptions, generics, and project layout.
java-patterns
Java: Spring Boot, CompletableFuture, records, sealed types, JPA/Hibernate, virtual threads. Triggers: Java, Spring, JPA, Hibernate, Maven, Gradle, virtual thread, sealed class.
java-coding-standards
A set of Java coding standards for Spring Boot services, covering naming, immutable data, optional values, streams, and exceptions.
123-java-design-patterns
Use when you need to select, review, or implement Java design and integration patterns — including classic Java design patterns, REST API patterns, Kafka and event-driven patterns, database and persistence patterns, and cross-cutting integration patterns. This should trigger for requests such as Apply Java design…