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 instructions/lsampaioweb/ai-instructions/spring-boot-api-versioninggit 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-api-versioning)<a href="https://agentmods.dev/instructions/lsampaioweb/ai-instructions/spring-boot-api-versioning"><img src="https://agentmods.dev/badge/instructions/lsampaioweb/ai-instructions/spring-boot-api-versioning.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.00549 | $0.00549 |
| Opus 5 | $0.00275 | $0.00275 |
| Sonnet 5 | $0.00110 | $0.00110 |
| Haiku 4.5 | $0.00055 | $0.00055 |
Grade A, and why
ai-instructions spring-boot-api-versioning.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 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 · 549 tokens per session scan A ba88fb427e23
ai-instructions spring-boot-api-versioning.instructions.md is an instructions file published in the GitHub repository lsampaioweb/ai-instructions (1 stars, last pushed 13d ago), licensed MIT. It adds 549 tokens to every session, about $0.0027 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
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).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
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.
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.
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.
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).