Borrowing it
Nothing to install: this file belongs to lsampaioweb/ai-instructions. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/lsampaioweb/ai-instructions/main/.github/instructions/spring-boot-pom.instructions.mdgit 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/instructions/lsampaioweb/ai-instructions/spring-boot-pom)<a href="https://agentmods.dev/instructions/lsampaioweb/ai-instructions/spring-boot-pom"><img src="https://agentmods.dev/badge/instructions/lsampaioweb/ai-instructions/spring-boot-pom.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.1 | $0.00902 | $0.00902 |
| Opus 5 | $0.00451 | $0.00451 |
| Sonnet 5 | $0.00180 | $0.00180 |
| Haiku 4.5 | $0.00090 | $0.00090 |
Grade A, and why
ai-instructions spring-boot-pom.instructions.md 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 — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spring Boot POM Engine
Naming Conventions
- Use
br.com.lsampaiowebas the standardgroupIdfor all modules unless the user explicitly requests a different organization namespace. - Set
<artifactId>and<name>to the same identifier in kebab-case. - When
<artifactId>already represents the primary feature/module name, treat that segment as canonical and do not duplicate it in planned Java package paths.
Rules
- Set the Spring Boot parent to version
4.1.0. - Set the Java version to
25. - Set
<version>to0.1.0as the default stable project version when the user has not specified a version. - Keep Spring Boot parent and plugin versions coherent.
- Declare
<relativePath />on the<parent>block to force Maven to resolve the parent from the remote repository. - Set
<description>to a one-sentence summary of the module's purpose. - Set
<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>in<properties>. - Add only dependencies required by the explicit feature scope.
- Before introducing code that imports a type from an optional module, verify that the required artifact is already declared in
pom.xmlor add it in the same change. - Resolve required artifacts from concrete imports and annotations first, then write or update source files that depend on them.
- Declare
<dependency>entries in this order: (1) Spring Boot starters, (2) third-party libraries, (3) internal or project-owned dependencies, (4) test-scoped dependencies. - Pin a
<version>on a dependency only when the Spring Boot parent BOM does not already manage it. - Extract pinned third-party versions into named
<properties>entries (e.g.,<springdoc.version>3.0.1</springdoc.version>) and reference them via${property}in dependency blocks. - Remove duplicate
<dependency>declarations and redundant<exclusion>entries. - Add a
<!-- <one-sentence explanation> -->comment on the line immediately above every<dependency>block stating why the dependency is needed. - Declare test-only dependencies with
<scope>test</scope>. - Keep compile/test artifact decisions deterministic: avoid speculative dependency additions that are not justified by concrete imports, annotations, or instruction-file mandates.
- When tests need
Pageableweb binding support, useorg.springframework.boot:spring-boot-data-commonswith<scope>test</scope>instead of adding alternate pagination helper libraries. - Declare
spring-boot-devtoolswith<scope>runtime</scope>and<optional>true</optional>when development-time auto-restart is needed. - When MapStruct is used, declare
org.mapstruct:mapstructas a compile dependency andorg.mapstruct:mapstruct-processorinannotationProcessorPathswithinmaven-compiler-plugin. - When Lombok is used, declare
org.projectlombok:lombokwith<scope>provided</scope>and add it toannotationProcessorPathswithinmaven-compiler-plugin. - Configure
<workingDirectory>${project.basedir}</workingDirectory>inspring-boot-maven-pluginto enable correct devtools auto-restart behavior.
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 · 47 lines · 902 tokens per session scan A c688bfd760f2
ai-instructions spring-boot-pom.instructions.md is an instructions file published in the GitHub repository lsampaioweb/ai-instructions (1 stars, last pushed 14d ago), licensed MIT. It adds 902 tokens to every session, about $0.0045 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-09-03.
Other instructions, from other repositories
vibe-coding-prompt-template backend.instructions.md
Instructions for KhazP/vibe-coding-prompt-template: Read AGENTS.md, agentdocs/techstack.md, and agentdocs/codepatterns.md.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.