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/lsampaioweb/ai-instructions/spring-boot-applicationgit clone --depth 1 https://github.com/lsampaioweb/ai-instructionsWhat 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.00309 |
| Opus 5 | $0.00000 | $0.00154 |
| Sonnet 5 | $0.00000 | $0.00062 |
| Haiku 4.5 | $0.00000 | $0.00031 |
Grade A, and why
spring-boot-application 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 2d 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
Spring Boot Application Entry-Point Engine
Naming Conventions
- Name the main class after the module using the
*Applicationsuffix with a meaningful module prefix (e.g.,HolidaysApplication,AccountingApplication). - Do not use the bare name
Application.
Rules
- Place the main class in the root of the base package (e.g.,
br.com.lsampaioweb.holidays), not inside a feature sub-package. - Declare the main class as
public. - Annotate the main class with
@SpringBootApplicationonly. - Keep the main class body limited to the
mainmethod that callsSpringApplication.run. - Place
@Enable*annotations (e.g.,@EnableScheduling,@EnableAsync,@EnableConfigurationProperties) on dedicated@Configurationclasses that own the corresponding concern. - Rely on
@SpringBootApplication's default component scan. - Do not specify
scanBasePackagesunless a cross-module scan is explicitly required and approved.
Safety Guards
- Never declare more than one
@SpringBootApplicationclass per runnable module. - Never override the default component-scan root without explicit user approval.
- Never implement
CommandLineRunnerorApplicationRunnerin the main 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.
- 2d ago First seen · 26 lines · 0 tokens per session scan A a753122b1821
spring-boot-application is a cursor rule published in the GitHub repository lsampaioweb/ai-instructions (1 stars, last pushed 10d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 309 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
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.