agentmods.dev

spring-boot-pom

spring-boot-pom is a cursor rule for Cursor from lsampaioweb/ai-instructions. It costs 0 tokens per session (885 once invoked), scanned A, original, MIT.

A set of rules for the Maven project file in a Spring Boot application. Maven is a tool that manages Java dependencies, plugins, and builds.

In plain words
What is it for?
It guides the parent Spring Boot version, Java version, package naming, dependency order, encoding, and module descriptions.
Why use it?
It keeps dependency choices, project metadata, Java versions, and build settings consistent across modules.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

not rated 1repo changed 24d ago A scan 0 tokens original MIT

Good fit It guides the parent Spring Boot version, Java version, package naming, dependency order, encoding, and module descriptions.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/lsampaioweb/ai-instructions/spring-boot-pom
View source ↗ lsampaioweb/ai-instructions
Install

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.

Clone the repo
git clone --depth 1 https://github.com/lsampaioweb/ai-instructions

Made for: Cursor.

Wrote 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.

agentmods badge for spring-boot-pom

README.md
[![agentmods](https://agentmods.dev/badge/rules/lsampaioweb/ai-instructions/spring-boot-pom/github.svg)](https://agentmods.dev/rules/lsampaioweb/ai-instructions/spring-boot-pom)
Your own site
<a href="https://agentmods.dev/rules/lsampaioweb/ai-instructions/spring-boot-pom"><img src="https://agentmods.dev/badge/rules/lsampaioweb/ai-instructions/spring-boot-pom/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.

agentmods 80×15 button for spring-boot-pom

Your own site · 80×15
<a href="https://agentmods.dev/rules/lsampaioweb/ai-instructions/spring-boot-pom"><img src="https://agentmods.dev/badge/rules/lsampaioweb/ai-instructions/spring-boot-pom.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 885 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00885
Opus 5.5 $0.00000 $0.00354
Sonnet 5.5 $0.00000 $0.00177
Haiku 4.5 $0.00000 $0.00089

Measured 24d ago against content hash 645cb094657d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

spring-boot-pom 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 24d 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.

.cursor/rules/spring-boot-pom.mdc · 74 lines

How it starts

The opening of the file, as written. The whole thing — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Spring Boot pom.xml Contract

Rules

Project coordinates

  • groupId is always br.com.lsampaioweb.

  • version keeps the -SNAPSHOT suffix during active development (e.g. 0.0.1-SNAPSHOT). Only drop -SNAPSHOT when an actual release is being cut via mvn release:prepare.

  • Set java.version (or compiler release) to 25 unless an approved ADR Instruction override names a different Java major.

  • Use the latest stable Spring Boot 4.x parent unless an approved ADR Instruction override names a different Boot line.

  • When the module needs Spring Cloud, import spring-cloud-dependencies using the release train that matches the Boot generation in the table below. Prefer the latest service release of that train (for Boot 4.1.x that means 2025.1.2 or newer). Do not invent train numbers; verify against https://spring.io/projects/spring-cloud when unsure.

    Spring Boot Spring Cloud release train
    4.1.x 2025.1.x (Oakwood), starting at 2025.1.2
    4.0.x 2025.1.x (Oakwood)

    The Cloud BOM may still list an older <spring-boot.version>; that is expected when the Boot parent already manages the Boot line. Compatibility is defined by the table above, not by copying the BOM's internal Boot property.

  • Never leave <url /> or <licenses><license /></licenses> as empty stub tags. If no real project URL or license has been decided, omit the tags entirely - ask the user rather than fabricating a license.

Source control metadata

  • Always include the <scm> block when the project has a git repository, added from project creation (not deferred to release time): 
    <scm>
  <developerConnection>scm:git:<repository-url></developerConnection>
  <tag>HEAD</tag>
</scm>

Dependency documentation

  • Every <dependency> has a one-line <!-- purpose --> comment placed directly above the <dependency> tag (not inside it) explaining why it is there.

Dependency ordering

  • Group and order dependencies as:
    1. Spring Boot / Spring Cloud / Spring Security starters (framework-provided). Within this group, spring-boot-devtools goes last since it is a dev-only convenience, not a feature starter.
    2. Third-party libraries (non-Spring groupIds: e.g. org.projectlombok, org.mapstruct, org.springdoc, org.postgresql, com.zaxxer), ordered alphabetically by artifactId.
    3. Internal/project-owned dependencies (for multi-module projects).
    4. Test-scoped dependencies, always last, regardless of groupId.

Read the full file on GitHub · 74 lines

Changes

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.

  1. 24d ago Changed · +42 lines 645cb094657d
  2. 1mo ago Changed · -10 lines bb7bbb0af56a
  3. 1mo ago First seen · 42 lines · 0 tokens per session scan A 58ed43dcd645

Subscribe to this mod's changes

spring-boot-pom is a cursor rule published in the GitHub repository lsampaioweb/ai-instructions (1 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 885 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.

JavaLanguages
Related

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.

holtwood/awesome-cursorrules-zh · 0 tokens

java-import-fqn

A Java code rule that requires using imports and short class names when class names do not conflict. Fully qualified names remain allowed for documented exceptions such as naming conflicts and certain strings.

henryxm/autumn · 443 tokens

gradle

Enforce modern Gradle build practices for Java and Android projects, focusing on Kotlin DSL, modularity, version catalogs, and performance optimizations.

sanjeed5/awesome-cursor-rules-mdc · 1,896 tokens

mockito

This guide provides definitive best practices for writing robust, maintainable, and readable unit tests using Mockito with JUnit 5, focusing on modern patterns and common pitfalls.

sanjeed5/awesome-cursor-rules-mdc · 1,653 tokens

graftcode-java

Mandatory Graftcode architecture rules for building Java backend services (plain Maven/Gradle modules exposed via Graftcode Gateway, not REST).

grft-dev/graftcode · 4,704 tokens

java-17-development-standards

Java-specific development standards following Effective Java, Google Java Style Guide, and modern Java 17 LTS best practices.

beettlle/pi-spine · 0 tokens