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.
git 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-vault)<a href="https://agentmods.dev/rules/lsampaioweb/ai-instructions/spring-boot-vault"><img src="https://agentmods.dev/badge/rules/lsampaioweb/ai-instructions/spring-boot-vault/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.
<a href="https://agentmods.dev/rules/lsampaioweb/ai-instructions/spring-boot-vault"><img src="https://agentmods.dev/badge/rules/lsampaioweb/ai-instructions/spring-boot-vault.svg" alt="Reviewed on agentmods" width="80" 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.00000 | $0.00594 |
| Opus 5.5 | $0.00000 | $0.00238 |
| Sonnet 5.5 | $0.00000 | $0.00119 |
| Haiku 4.5 | $0.00000 | $0.00059 |
Grade A, and why
spring-boot-vault 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 14d 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spring Cloud Vault Integration Contract
Apply this contract only when a Spring Boot application integrates with Vault. It governs the client, not Vault server provisioning or secret-engine setup.
Pom owns the Boot ↔ Cloud BOM train. Configuration owns profiles and secrets.
TLS owns certificate validation. Architecture and testing own boundaries and
verification. Do not build a custom RestClient for Vault.
Dependency
- Import
spring-cloud-dependenciesas a BOM; choose the train from the pom contract (Boot 4.1.x:2025.1.2or newer). Do not pin Vault starter versions outside the BOM. - Add
spring-cloud-starter-vault-config.
Startup secrets
- Prefer Config Data (
spring.config.importwithvault:///...) for secrets required at startup. - Use an explicit import context and property prefix when binding KV keys.
- Set
spring.cloud.vault.kv.backendandbackend-versionto match the mount (version 2 only for KV v2). - Keep import path, mount, and secret path consistent when the same data is also read at runtime.
- Set
spring.cloud.vault.fail-fast: truewhen the app cannot start without Vault. - Bind through
@ConfigurationPropertiesand reject missing/blank required keys at startup; fail-fast alone does not validate individual keys.
Authentication and transport
- Supply tokens or auth credentials from the environment or a secret store.
- Prefer a scoped production identity over a local root/dev token.
- Use HTTPS for production Vault and keep certificate validation enabled.
- Never log token or secret values.
Explicit runtime reads
- Use
VaultOperationsonly when Config Data is not enough. - For KV v2, use
opsForVersionedKeyValue(mountPath).get(secretPath)and validate the data; do not hand-parse Vault HTTP envelopes. - Static KV values are not renewable leases. Add scheduled polling only when the feature explicitly needs runtime refresh, and replace the cache atomically after validating required keys.
Testing
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.
- 14d ago First seen · 65 lines · 0 tokens per session scan A 4a7fb72005bb
spring-boot-vault is a cursor rule published in the GitHub repository lsampaioweb/ai-instructions (1 stars, last pushed 14d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 594 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-10-04.
Other cursor rules, from other repositories
api-property-optionality-hygiene
Fix ApiProperty/ApiPropertyOptional optionality mismatches in DTO files; use for scheduled batch fixes or DTO edits.
python
Python best practices and patterns for modern software development with Flask and SQLite.
cursor
You are working on the checkout service. Preserve transaction integrity and auditability.
django
Definitive guidelines for writing maintainable, performant, and secure Django applications, emphasizing modern best practices, clear code organization, and efficient patterns.
shared-libraries
Shared libraries - condition framework, inventory containers, file-backed DB, itinerary, references.
selectools-providers
Rules for working with LLM provider adapters in selectools.