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-api-versioninggit 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.00554 |
| Opus 5 | $0.00000 | $0.00277 |
| Sonnet 5 | $0.00000 | $0.00111 |
| Haiku 4.5 | $0.00000 | $0.00055 |
Grade A, and why
spring-boot-api-versioning 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.
How it starts
The opening of the file, as written. The whole thing — 36 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spring Boot API-Versioning Engine
Rules
- Use URL path versioning with an explicit
/api/v1prefix for all REST endpoints. - Use integer version numbers in the format
/api/vN(e.g.,/api/v1,/api/v2). - Do not use floating-point or date-based version identifiers such as
/api/v1.1or/api/2024-01. - Exclude MVC page controllers and view routes from API version-prefix enforcement.
- Use one canonical versioning strategy across the entire project.
- Declare version changes explicitly in controller route mappings.
- Declare a shared base-path constant at the controller class level when the versioned route is reused across methods.
- Keep v1 changes additive and backward compatible.
- Treat these changes as additive and backward compatible: adding optional request fields with defaults, adding new response fields, and adding new endpoints.
- Create a new API version for every breaking contract change.
- Treat these changes as breaking: removing or renaming a field, changing a field type, making an optional field required, removing an endpoint, changing an endpoint path, or changing an HTTP method.
- Keep request and response DTO changes backward compatible within the same version.
- Use version-specific DTO suffixes when payload contracts diverge across versions (e.g.,
HolidayV1Response,HolidayV2Response). - Share the same DTO across versions only when the payload contract is identical.
- Keep route versioning distinct from OpenAPI document version metadata.
- Keep controller tests aligned with the active versioned route prefix.
- When v2 or later is introduced, keep old and new versions available side by side until the old version is explicitly deprecated.
- When v2 or later is introduced, document migration notes and client impact.
- Announce a deprecated API version via a
Deprecationresponse header per RFC 8594. - Announce a deprecated API version via a
Sunsetresponse header per RFC 8594. - Always set both
DeprecationandSunsetheaders together when a version is scheduled for removal. - Maintain a deprecated API version for at least one full release cycle after the deprecation announcement; remove a version only in a later release than the one that deprecates it.
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 · 36 lines · 0 tokens per session scan A 4533ab5cc52b
spring-boot-api-versioning 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 554 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.