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-events)<a href="https://agentmods.dev/rules/lsampaioweb/ai-instructions/spring-boot-events"><img src="https://agentmods.dev/badge/rules/lsampaioweb/ai-instructions/spring-boot-events/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-events"><img src="https://agentmods.dev/badge/rules/lsampaioweb/ai-instructions/spring-boot-events.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.00505 |
| Opus 5.5 | $0.00000 | $0.00202 |
| Sonnet 5.5 | $0.00000 | $0.00101 |
| Haiku 4.5 | $0.00000 | $0.00051 |
Grade A, and why
spring-boot-events 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spring Boot Application Events Contract
Apply this contract only for in-process Spring application events
(ApplicationEventPublisher / @EventListener). It does not cover Redis Pub/Sub,
RabbitMQ, or other brokers.
Architecture owns feature packages, service boundaries, and constructor injection.
Controller owns REST boundaries. Logging and i18n own log message keys.
@EnableAsync, executors, and general @Async method rules belong to the async
contract — this file only says when an event listener may be async.
When to use
- Use application events to let one feature react to another without injecting that feature's service.
- Prefer a direct method call when both sides are the same feature and a listener would only add indirection.
Event type
- Model payloads as immutable records in the feature package.
- Put in the event only what listeners need. Prefer metadata (ids, lengths, locale tags, timestamps) over copying large or sensitive bodies.
- Capture thread-local values before publish and pass them in the event (for example
LocaleContextHolder); do not rely on request thread-locals inside@Asynclisteners.
Publishing
- Publish through a dedicated feature component that wraps
ApplicationEventPublisher. - Call the publisher from the service (or equivalent application component), not from the REST controller.
Listening
- Handle events with
@EventListeneron a dedicated component in the feature package. - Keep listener methods focused on one reaction (audit, metrics, side effect).
- Prefer synchronous listeners for simple in-memory work. Add
@Asyncon a listener only when that reaction is blocking or latency-sensitive, and enable async per the async contract (@EnableAsyncon the application).
Forbidden
- Never publish application events from a REST controller.
- Never inject another feature's service solely to trigger a side effect that an event listener should own.
- Never put large request bodies or secrets into event payloads when metadata is enough.
- Never treat application events as a durable or cross-process messaging solution (use RabbitMQ or Redis Pub/Sub contracts instead).
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 · 59 lines · 0 tokens per session scan A b69bcca0e795
spring-boot-events 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 505 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.