Borrowing it
Nothing to install: this file belongs to lsampaioweb/ai-instructions. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/lsampaioweb/ai-instructions/main/.github/instructions/spring-boot-websocket.instructions.mdgit 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-websocket)<a href="https://agentmods.dev/instructions/lsampaioweb/ai-instructions/spring-boot-websocket"><img src="https://agentmods.dev/badge/instructions/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.00392 | $0.00392 |
| Opus 5 | $0.00196 | $0.00196 |
| Sonnet 5 | $0.00078 | $0.00078 |
| Haiku 4.5 | $0.00039 | $0.00039 |
Grade A, and why
ai-instructions spring-boot-websocket.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 4d 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.
- Permit 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 destinations and broadcast target addresses statically defined as constants.
- Route all
SimpMessagingTemplateandApplicationEventPublishercalls through a dedicated event publisher class. - Track WebSocket session lifecycle (connect/disconnect) events in a dedicated
@Component, not in message handler classes.
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.
- 4d ago First seen · 32 lines · 392 tokens per session scan A ef85a8542c62
ai-instructions spring-boot-websocket.instructions.md is an instructions file published in the GitHub repository lsampaioweb/ai-instructions (1 stars, last pushed 15d ago), licensed MIT. It adds 392 tokens to every session, about $0.0020 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
vibe-coding-prompt-template backend.instructions.md
Instructions for KhazP/vibe-coding-prompt-template: Read AGENTS.md, agentdocs/techstack.md, and agentdocs/codepatterns.md.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).