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-async-eventsgit 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-async-events)<a href="https://agentmods.dev/rules/lsampaioweb/ai-instructions/spring-boot-async-events"><img src="https://agentmods.dev/badge/rules/lsampaioweb/ai-instructions/spring-boot-async-events.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.00000 | $0.00514 |
| Opus 5 | $0.00000 | $0.00257 |
| Sonnet 5 | $0.00000 | $0.00103 |
| Haiku 4.5 | $0.00000 | $0.00051 |
Grade A, and why
spring-boot-async-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 5d 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 Async Events
Naming Conventions
- Name event classes using past-tense domain verbs with the
*Eventsuffix (e.g.,UserCreatedEvent,OrderShippedEvent). - Do not use present-tense or generic event names such as
UserEventorDataChangedEvent.
Rules
- Keep events immutable and self-contained.
- Keep publication logic isolated in dedicated publisher components.
- Keep listener responsibilities single-purpose and side-effect scoped.
- Keep thread-local or request-derived data extracted before async handoff when it is needed after dispatch.
- Keep locale, security, tracing, and request-derived values copied into the event payload before async handoff when listeners require them.
- Keep async enablement explicit at application configuration level when Spring application events or method-level async execution are used.
- Keep asynchronous execution boundaries explicit in the transport or framework model.
- Treat broker-managed listeners as explicit async boundaries when messaging infrastructure controls dispatch.
- Design listener logic to be idempotent.
- Place blocking workloads in dedicated listener classes with an explicit threadpool, error handling strategy, and failure propagation model defined in configuration.
- Keep publisher and consumer failure strategies explicit for non-trivial async flows.
- Configure a dead-letter queue (DLQ) for every broker-backed message queue that has business significance.
- Declare a
JacksonJsonMessageConverterbean in the broker configuration class to enable JSON serialization forRabbitTemplateand@RabbitListenerbindings. - Declare all business-significance broker queues as durable.
- Use
DirectExchangefor routing-key-based delivery,FanoutExchangefor broadcast to all bound queues, andTopicExchangefor wildcard routing patterns. - Serialize broker event payloads as JSON by default.
- Use typed deserialization targets at the consumer boundary.
- Always call
Thread.currentThread().interrupt()after catchingInterruptedExceptionin a listener before returning or rethrowing.
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.
- 5d ago First seen · 36 lines · 0 tokens per session scan A 01cbe6113a05
spring-boot-async-events is a cursor rule published in the GitHub repository lsampaioweb/ai-instructions (1 stars, last pushed 13d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 514 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
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
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.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.