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 rules/jabrena/cursor-rules-spring-boot/301-frameworks-spring-boot-coregit clone --depth 1 https://github.com/jabrena/cursor-rules-spring-bootWrote 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/jabrena/cursor-rules-spring-boot/301-frameworks-spring-boot-core)<a href="https://agentmods.dev/rules/jabrena/cursor-rules-spring-boot/301-frameworks-spring-boot-core"><img src="https://agentmods.dev/badge/rules/jabrena/cursor-rules-spring-boot/301-frameworks-spring-boot-core.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.00000 | $0.07073 |
| Opus 5 | $0.00000 | $0.03537 |
| Sonnet 5 | $0.00000 | $0.01415 |
| Haiku 4.5 | $0.00000 | $0.00707 |
Grade A, and why
301-frameworks-spring-boot-core 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 — 1,208 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spring Boot Core
Spring Boot Core guidelines focus on proper usage of main annotations, bean management, and configuration best practices to build maintainable and efficient Spring Boot applications.
Implementing These Principles
These guidelines are built upon the following core principles:
- Principle 1: Use appropriate Spring annotations to clearly express component responsibilities
- Principle 2: Leverage Spring's dependency injection and IoC container effectively
- Principle 3: Follow configuration best practices for maintainable and testable applications
- Principle 4: Apply proper bean lifecycle management and scoping
Table of contents
- Rule 0: Spring Boot Main Application Class
- Rule 1: Main Spring Boot Annotations Usage
- Rule 2: Bean Definition and Management
- Rule 3: Configuration Classes and Properties
- Rule 4: Component Scanning and Package Organization
- Rule 5: Conditional Configuration and Profiles
- Rule 6: Constructor Dependency Injection Best Practices
- Rule 7: Bean Minimization and Composition
- Rule 8: Scheduled Tasks and Background Processing
Rule 0: Spring Boot Main Application Class
Title: Create a Proper Spring Boot Main Application Class Description: Every Spring Boot application should have a main application class annotated with @SpringBootApplication. This class serves as the entry point and configuration root, combining @Configuration, @EnableAutoConfiguration, and @ComponentScan annotations.
Good example:
@SpringBootApplication
public class MainApplication {
public static void main(String[] args) {
SpringApplication.run(MainApplication.class, args);
}
}
// For more complex scenarios with custom configuration
@SpringBootApplication(
scanBasePackages = {
"com.company.app.controller",
"com.company.app.service",
"com.company.app.repository",
"com.company.app.config"
},
exclude = {
DataSourceAutoConfiguration.class,
SecurityAutoConfiguration.class
}
)
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 · 1,208 lines · 0 tokens per session scan A 5b2e261d70e3
301-frameworks-spring-boot-core is a cursor rule published in the GitHub repository jabrena/cursor-rules-spring-boot (47 stars, last pushed 5mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 7,073 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-30.
Other cursor rules, from other repositories
backend
Backend Java — Spring Boot controllers/services, JUnit controller tests, MakeMe. Read this first for any backend work.
java-import-fqn
Java 禁止不必要的全限定类名,必须 import(类名冲突除外).
springboot-jpa-best-practices
Java Spring Boot + JPA 项目最佳实践,涵盖分层架构、注解、事务、异常处理、安全与代码风格等。.
java
Cursor rule "java" from themoah/klag, covering java conventions, testing and kafka client notes.
component-parameter-key-no-dot
@ComponentParameter 的 key 禁止包含 ".",统一使用下划线 / 顶层扁平命名.
java-openapi-annotations
生成 REST 接口时自动补充 OpenAPI 3(springdoc)注解.