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-websocket)<a href="https://agentmods.dev/rules/lsampaioweb/ai-instructions/spring-boot-websocket"><img src="https://agentmods.dev/badge/rules/lsampaioweb/ai-instructions/spring-boot-websocket.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.00370 |
| Opus 5 | $0.00000 | $0.00185 |
| Sonnet 5 | $0.00000 | $0.00074 |
| Haiku 4.5 | $0.00000 | $0.00037 |
Grade A, and why
spring-boot-websocket 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 7d 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.
What it actually says
Spring Boot WebSocket
Rules
- Keep STOMP endpoint and destination prefixes explicit.
- Declare all STOMP destination prefix strings as
private static final Stringconstants in the configuration class. - Use
/appas the application destination prefix for client-to-server messages. - Use
/topicfor server-to-client broadcast subscriptions. - Use
/queuefor point-to-point messages. - Use
/wsas the default STOMP endpoint path unless the module explicitly requires a different path. - Call
.withSockJS()on every STOMP endpoint registration for browser transport fallback compatibility. - Keep allowed-origin strategy externalized through configuration.
- Allow wildcard origins only for explicitly documented development or local profiles.
- Require constrained origin patterns for production profiles.
- Authenticate WebSocket connections at the HTTP handshake phase using the same authentication token as REST endpoints.
- Configure heartbeat intervals explicitly (
outgoingHeartbeat=10000ms,incomingHeartbeat=10000ms). - Annotate every STOMP message handler parameter with
@Payloadto make the message source explicit. - Use declarative
@SendTofor simple, single-destination broadcasts. - Use
SimpMessagingTemplatewhen the broadcast destination is dynamic or computed at runtime. - Keep message mapping and broadcast targets deterministic.
- Keep event publication isolated from transport handlers.
- Keep connection state tracking in dedicated components.
- Keep websocket and REST status contracts aligned.
Safety Guards
- Never expose websocket endpoints with uncontrolled origin policy.
- Never allow unauthenticated connections to application-level STOMP destinations.
- Never couple broker configuration changes with unrelated features.
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.
- 7d ago First seen · 33 lines · 0 tokens per session scan A 39b7a4ab152d
spring-boot-websocket 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 370 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
python
Python best practices and patterns for modern software development with Flask and SQLite.
api-property-optionality-hygiene
Fix ApiProperty/ApiPropertyOptional optionality mismatches in DTO files; use for scheduled batch fixes or DTO edits.
django
Definitive guidelines for writing maintainable, performant, and secure Django applications, emphasizing modern best practices, clear code organization, and efficient patterns.
cursor
You are working on the checkout service. Preserve transaction integrity and auditability.
shared-libraries
Shared libraries - condition framework, inventory containers, file-backed DB, itinerary, references.
env-validation-gate
Env validation gate — every app with ≥1 required env var validates its contract at boot via Zod; raw process.env is banned outside the env module. Full pattern in .claude/skills/t2000-env-gate/.