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 skills/iambrzdev/enterprise-agent-skills/java-spring-enterprisenpx skills add iamBrzDev/enterprise-agent-skills --skill java-spring-enterprisegit clone --depth 1 https://github.com/iamBrzDev/enterprise-agent-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/iambrzdev/enterprise-agent-skills/java-spring-enterprise)<a href="https://agentmods.dev/skills/iambrzdev/enterprise-agent-skills/java-spring-enterprise"><img src="https://agentmods.dev/badge/skills/iambrzdev/enterprise-agent-skills/java-spring-enterprise.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.00113 | $0.02237 |
| Opus 5 | $0.00056 | $0.01118 |
| Sonnet 5 | $0.00023 | $0.00447 |
| Haiku 4.5 | $0.00011 | $0.00224 |
Grade A, and why
java-spring-enterprise 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 3d 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 — 293 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When to activate
- Scaffolding a new Spring Boot enterprise project
- "How do I structure this feature?" in a Java/Spring context
- Designing a service layer, use case, or domain model
- Configuring
@Transactional— any question about transactions, isolation, or rollback - Setting up HikariCP connection pool tuning
- Implementing Virtual Threads (Java 21+) for I/O-heavy operations
- Adding observability: Micrometer, Prometheus, Grafana, OpenTelemetry tracing
- Refactoring a fat controller or a service with too many responsibilities
- Any mention of Hexagonal Architecture, ports/adapters, DDD, or use cases in Java
Rules — Non-negotiable
-
No business logic in controllers. Controllers receive HTTP input, delegate to a use case or service, and return a response. Nothing else.
-
Domain layer has zero Spring dependencies. Entities and domain services must not import Spring annotations. Domain is framework-agnostic.
-
@Transactionalis not a default annotation. Apply it deliberately, with the correct isolation level. AddreadOnly = truefor all read operations. -
Never expose domain entities in API responses. Always map to DTOs or response records before returning from the controller.
-
HikariCP pool size must be tuned explicitly. The default pool size (10) is wrong for most enterprise workloads. Always configure based on load profile.
Project Structure — Clean / Hexagonal Architecture
src/main/java/com/company/app/
├── domain/
│ ├── model/ # Entities, Value Objects, Aggregates — NO Spring here
│ ├── port/
│ │ ├── in/ # Use case interfaces (driving ports)
│ │ └── out/ # Repository + external service interfaces (driven ports)
│ └── service/ # Domain services — pure business logic
│
├── application/
│ └── usecase/ # Use case implementations — orchestrate domain + ports
│ ├── CreateOrderUseCase.java
│ └── GetOrderByIdUseCase.java
│
├── adapter/
│ ├── in/
│ │ └── web/ # Controllers, request/response DTOs, mappers
│ └── out/
│ ├── persistence/ # JPA entities, repositories (Spring Data)
│ └── external/ # HTTP clients, message producers
│
└── config/ # Spring configuration, beans, security
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.
- 3d ago First seen · 293 lines · 113 tokens per session scan A ce3aaea6d3cf
java-spring-enterprise is a skill published in the GitHub repository iamBrzDev/enterprise-agent-skills (5 stars, last pushed 5mo ago), licensed MIT. It adds 113 tokens to every session and 2,237 once invoked, about $0.0006 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-31.
Other skills, from other repositories
opik-backend
Java backend patterns for Opik. Use when working in apps/opik-backend, designing APIs, database operations, or services.
add-java-code-snippets-in-docs
Use when the user asks to add Java tabs/examples to mkdocs docs that already have Kotlin examples (files under docs/docs/.md using === "Kotlin" / Knit INCLUDE+SUFFIX blocks). Handles mkdocs-material tabs, Knit directives, @JavaAPI bridge methods, and JVM factory classes.
wxjava-troubleshooter
排查 WxJava 在配置初始化、access token、签名验签、支付证书、回调通知、序列化、网络请求和多账号隔离方面的问题。适用于用户提供异常、日志、请求响应或“WxJava 为什么不能调用”的场景。.
wxjava-api-contributor
按 WxJava 的 Maven 多模块、Java 8、公共 API 兼容性和 TestNG 约定,为微信官方接口新增或维护 SDK 支持。适用于新增 Service API、请求响应 Bean、序列化、HTTP 实现、Starter 配置或回归测试时。.
wxjava-upgrade-guide
规划 WxJava 的版本升级与迁移,检查 BOM、模块依赖、Java 版本、配置与公共 API 兼容性,并提供可回滚的验证步骤。适用于用户从旧版升级、切换依赖管理方式、处理兼容性告警或制定升级发布计划时。.
union-type-wrappers
Add typed getters and setters over BinaryData properties that represent TypeSpec union types in generated Java models. Use when generated classes expose BinaryData for union-typed fields and you need ergonomic, type-safe accessors instead.