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.
git clone --depth 1 https://github.com/lsampaioweb/ai-instructionsWrote 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/rules/lsampaioweb/ai-instructions/spring-boot-architecture)<a href="https://agentmods.dev/rules/lsampaioweb/ai-instructions/spring-boot-architecture"><img src="https://agentmods.dev/badge/rules/lsampaioweb/ai-instructions/spring-boot-architecture/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/rules/lsampaioweb/ai-instructions/spring-boot-architecture"><img src="https://agentmods.dev/badge/rules/lsampaioweb/ai-instructions/spring-boot-architecture.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00000 | $0.01016 |
| Opus 5.5 | $0.00000 | $0.00406 |
| Sonnet 5.5 | $0.00000 | $0.00203 |
| Haiku 4.5 | $0.00000 | $0.00102 |
Grade A, and why
spring-boot-architecture 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 17d 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spring Boot Java Architecture Contract
Package organization
- Organize application code by business feature, not by technical layer.
- Keep a feature's controller, service, service implementation, repository contract, repository implementation, domain model, request/response DTOs, mapper, and feature exceptions in that feature package.
- Use dedicated shared packages only for genuinely cross-cutting infrastructure such as configuration, exception handling, internationalization, OpenAPI setup, persistence configuration, filters, and event infrastructure.
- Do not create broad top-level
controller,service,repository,model, ordtopackages that collect classes from multiple business features.
Dependency direction
- Controllers, page controllers, and message endpoints depend on service interfaces only.
- Services depend on repository interfaces, mappers, and shared infrastructure as needed.
- Repository implementations contain persistence or external-data access and are hidden behind repository interfaces.
- Controllers must never inject or call repository classes directly.
- Do not place business rules, persistence calls, or DTO mapping logic in controllers.
- Keep dependency injection constructor-based; do not use field injection.
Services
- Every application feature has a service interface and a separate implementation class:
<Feature>Serviceand<Feature>ServiceImpl. - Annotate only the implementation with
@Service. - Put business orchestration, transaction boundaries, authorization checks that belong to the application service, and conversion coordination in the service implementation.
- A service may be thin when the feature has little business logic, but do not bypass the service layer for convenience.
Repositories
- Every repository has an interface and a separate implementation class:
<Feature>Repositoryand<Feature>RepositoryImpl. - Annotate only the implementation with
@Repository. - Keep database, cache, or external-system access inside the repository implementation.
- Keep the persistence technology behind the repository interface so implementations can be replaced or tested independently.
- Do not expose JDBC templates, Redis operations,
RestClient, or vendor-specific types through service or controller contracts. - The default relational persistence approach is Spring JDBC, not ORM.
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.
- 17d ago Changed · +57 lines 05aac971523a
- 1mo ago Changed · -28 lines 5e7005bb8c9b
- 1mo ago First seen · 76 lines · 0 tokens per session scan A cdd9ee76de33
spring-boot-architecture is a cursor rule published in the GitHub repository lsampaioweb/ai-instructions (1 stars, last pushed 18d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,016 tokens. 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 cursor rules, from other repositories
springboot-jpa-best-practices
A set of Chinese-language rules for structuring Java Spring Boot applications that use JPA, a library for database access.
graftcode-java
Mandatory Graftcode architecture rules for building Java backend services (plain Maven/Gradle modules exposed via Graftcode Gateway, not REST).
spring-retry-conventions
Spring Boot database retry conventions using AbstractDatabaseService and RetryTemplate.
java-springboot-standards
Java Spring Boot coding standards and patterns for your monorepo services.
spring-boot
Spring Boot: annotations, dependency injection, JPA patterns.
http-clients
RestClient and declarative HTTP interfaces for calling backend APIs - Spring Boot 4+.