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-enumgit 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-enum)<a href="https://agentmods.dev/instructions/lsampaioweb/ai-instructions/spring-boot-enum"><img src="https://agentmods.dev/badge/instructions/lsampaioweb/ai-instructions/spring-boot-enum.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.00451 | $0.00451 |
| Opus 5 | $0.00226 | $0.00226 |
| Sonnet 5 | $0.00090 | $0.00090 |
| Haiku 4.5 | $0.00045 | $0.00045 |
Grade A, and why
ai-instructions spring-boot-enum.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 — 34 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spring Boot Enum
Naming Conventions
- Use the
*Enumsuffix for all enum class names (e.g.,UserStatusEnum,OrderStateEnum). - Include the domain context as a prefix in every enum class name (e.g.,
UserStatusEnum, notStatusEnum). - Use domain-specific enum names (never
TypeEnum,StatusEnum, or other generic names without a domain prefix).
Rules
- Keep enum values stable after public release.
- Treat adding a new enum value to a public API contract as a breaking change.
- Document new enum value additions in the API changelog.
- Keep enum names expressive and domain-specific.
- Keep enum-to-string behavior explicit when used in contracts.
- Serialize enums as their
name()string value in all API and message contracts (not ordinal). - Apply
@JsonValueonly when the serialized API value must differ from the Java constant name. - Declare a
@JsonCreatorfactory method on enums used in API request bodies to control string-to-enum deserialization. - Add an
UNKNOWNfallback constant annotated with@JsonEnumDefaultValuewhen the enum is sourced from an external API or message broker that may introduce new values. - Store application-owned enum domains in relational persistence through a dedicated lookup/reference table plus a foreign-key column in the business table.
- Keep a stable code column in the lookup/reference table for mapping between the Java enum
name()and the relational row. - Store enum values as strings in relational persistence only when the enum is external-system-owned, transient, or the user explicitly rejects a lookup/reference table design.
- Declare enum constructor parameters as
privateand their backing fields asfinal. - Keep helper methods deterministic and side-effect free.
Safety Guards
- Never repurpose existing enum values for new semantics.
- Never introduce contract-breaking enum changes silently.
- Never duplicate enum meaning in string literals across code.
- Never use ordinal-style numeric persistence to represent enum meaning directly in a business table.
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 · 34 lines · 451 tokens per session scan A 9fbecec57efd
ai-instructions spring-boot-enum.instructions.md is an instructions file published in the GitHub repository lsampaioweb/ai-instructions (1 stars, last pushed 13d ago), licensed MIT. It adds 451 tokens to every session, about $0.0023 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
questdb CLAUDE.md
Claude Code instructions for questdb/questdb, covering claude.md, project overview, coding guidelines, tests and questdb's sql dialect.
liteflow CLAUDE.md
Instructions for dromara/liteflow, covering claude.md, 概述, 命令, 构建 and 构建整个项目（模块集由 jdk 版本自动选择 —— 见下方说明）.
BitcoinAddressFinder CLAUDE.md
Claude Code instructions for bernardladenthin/BitcoinAddressFinder, covering claude.md — bitcoinaddressfinder, project overview, build system, common commands and compile only.
imgui-java CLAUDE.md
Claude Code instructions for SpaiR/imgui-java: This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
nano CLAUDE.md
Claude Code instructions for NanoNative/nano, covering claude.md, project overview, build & development commands, maven commands and graalvm native image.
langchain4j-cdi copilot-instructions.md
Copilot instructions for langchain4j/langchain4j-cdi, covering langchain4j cdi integration, working effectively, prerequisites, bootstrap and build and essential commands.