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-gitignoregit 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-gitignore)<a href="https://agentmods.dev/rules/lsampaioweb/ai-instructions/spring-boot-gitignore"><img src="https://agentmods.dev/badge/rules/lsampaioweb/ai-instructions/spring-boot-gitignore.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.00399 |
| Opus 5 | $0.00000 | $0.00199 |
| Sonnet 5 | $0.00000 | $0.00080 |
| Haiku 4.5 | $0.00000 | $0.00040 |
Grade A, and why
spring-boot-gitignore 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.
What it actually says
Spring Boot .gitignore Engine
Rules
- Every Spring Boot project must have a
.gitignoreat the repository root. - Group exclusion rules by category with a
#comment header above each group. - Exclude
target/for Maven build output. - Exclude Maven Release plugin artifacts:
release.properties,pom.xml.releaseBackup. - Exclude IntelliJ IDEA artifacts:
.idea/,*.iml,*.iws,*.ipr. - Exclude Eclipse and STS artifacts:
.project,.classpath,.factorypath,.settings/,.apt_generated,.sts4-cache. - Exclude
.vscode/for VS Code workspace artifacts. - Allow
.vscode/extensions.jsonand.vscode/settings.jsonas tracked exceptions using!negation patterns. - Exclude OS artifacts:
.DS_Store,Thumbs.db. - Exclude secrets and local overrides:
*.env,.env,application-local.yml,application-local.properties. - Exclude TLS credential files:
*.p12,*.crt,*.key,*.pfx. - Exclude log output directories and files:
logs/,*.log,*.gz. - Exclude JVM crash log files:
hs_err_pid*.
Safety Guards
- Never commit
application-local.*files; they are runtime-only overrides containing environment-specific secrets. - Never commit TLS credential files to source control.
- Never use glob patterns (
target/*) where directory patterns (target/) are more precise and cover nested paths. - Never exclude the
.mvn/directory when it contains the Maven wrapper; the wrapper is intentionally tracked.
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 · 28 lines · 0 tokens per session scan A 667ab6d75895
spring-boot-gitignore is a cursor rule published in the GitHub repository lsampaioweb/ai-instructions (1 stars, last pushed 11d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 399 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.