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/loiane/specs-driven-development-spring-angular/spring-boot-4-conventionsnpx skills add loiane/specs-driven-development-spring-angular --skill spring-boot-4-conventionsgit clone --depth 1 https://github.com/loiane/specs-driven-development-spring-angularWrote 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/loiane/specs-driven-development-spring-angular/spring-boot-4-conventions)<a href="https://agentmods.dev/skills/loiane/specs-driven-development-spring-angular/spring-boot-4-conventions"><img src="https://agentmods.dev/badge/skills/loiane/specs-driven-development-spring-angular/spring-boot-4-conventions.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.00050 | $0.03332 |
| Opus 5 | $0.00025 | $0.01666 |
| Sonnet 5 | $0.00010 | $0.00666 |
| Haiku 4.5 | $0.00005 | $0.00333 |
Grade A, and why
spring-boot-4-conventions 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 — 243 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spring Framework 7 / Spring Boot 4 conventions
Java 25 + Spring Framework 7 + Spring Boot 4. Prefer the most modern idiom unless an ADR explains otherwise.
Defaults to apply
Package layout — by feature, not by layer
Top-level packages are bounded contexts / features, not technical layers.
Inside a feature, split by visibility (api published, private impl hidden).
For the private impl sub-packages, apply the following rule:
- One class of a given type (single entity, single service, etc.) — keep it directly in the feature package (no sub-package).
- Multiple classes of the same type — use a typed sub-package within the feature:
model/— JPA entitiesrepository/— Spring Data repositoriesservice/— service classes / implementationsservice/— service implementations
- Inside
api/— keep the controller (or service interface) at theapi/level; put all request/response DTO records in anapi/dto/sub-package.
All classes in the feature's private sub-packages (model, repository, service, internal) must be public (cross-package visibility is required when code spans multiple sub-packages). Cross-feature access is still forbidden and enforced by ArchUnit — public here means "visible within this feature", not "part of the published API".
The api/ sub-package is the only published surface. Other features depend only on <feature>.api.
com.example.checkout
├── giftcard/ # feature/domain — one package per bounded context
│ ├── api/ # published surface: controller, service interfaces, events
│ │ ├── GiftCardController.java
│ │ ├── GiftCardRedemptionService.java
│ │ ├── GiftCardRedeemed.java
│ │ ├── dto/ # request/response DTOs always in api/dto/
│ │ │ ├── RedeemCommand.java
│ │ │ └── GiftCardRedemptionResponse.java
│ │ └── exception/ # domain exceptions thrown by this feature's services
│ │ └── InsufficientBalanceException.java
│ ├── model/ # entities (multiple → typed sub-package)
│ │ ├── GiftCardEntity.java
│ │ └── GiftCardTransactionEntity.java
│ ├── repository/ # repositories (multiple → typed sub-package)
│ │ ├── GiftCardRepository.java
│ │ └── GiftCardTransactionRepository.java
│ └── service/ # service implementations (multiple → typed sub-package)
│ └── GiftCardRedemptionServiceImpl.java
├── order/ # another feature
│ ├── api/
│ │ └── dto/ # DTOs always in api/dto/
│ │ └── OrderSummaryResponse.java
│ └── service/ # single service impl — sub-package still used for consistency
│ └── OrderService.java
└── shared/ # cross-cutting: error envelope, security config, time
└── exception/ # GlobalExceptionHandler (@RestControllerAdvice)
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 · 243 lines · 50 tokens per session scan A 2c1db1b4bec3
spring-boot-4-conventions is a skill published in the GitHub repository loiane/specs-driven-development-spring-angular (58 stars, last pushed 2mo ago), licensed MIT. It adds 50 tokens to every session and 3,332 once invoked, about $0.0003 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 skills, from other repositories
java-springboot
Spring Boot best practices — concise reference.
spring-boot
Spring Boot 3.x - Java framework for production-ready applications with dependency injection, REST APIs, data access, security, and actuator monitoring.
mica-admin-backend
Use when adding, modifying or reviewing backend code in mica-admin-server (Spring Boot 4.1 + MyBatis-Plus + Spring Security). Covers the 6-file CRUD module recipe (entity/query/mapper/service/impl/controller), response conventions (success returns raw body, code=0 only on error), @ApiLog audit logging, @PreAuthorize…
spring-boot-dev
Build, test, and run Spring Boot applications using Arconia CLI. Use when working on a Java or Spring Boot project and you need to compile the application, run tests, start the app in development mode, build a GraalVM native executable, or run the application locally with dev services. Also use when the user asks to…
spring-boot-upgrade
Upgrade Spring Boot, Spring AI, Arconia Framework, Gradle, or Maven versions using Arconia CLI. Use when the user wants to upgrade or update their project's framework version, migrate to a newer Spring Boot or Spring AI release, update the Gradle or Maven wrapper, or bring dependencies to their latest versions. Also…
spring-boot-create
Create a new Spring Boot project from a template using Arconia CLI. Use when the user wants to start a new Java or Spring Boot application, scaffold a project, bootstrap a new service, generate a new app from a template, or initialize a new project. Also use when the user mentions creating a project with specific…