ai-instructions: Instructions file for GitHub Copilot

.github/instructions/spring-boot-websocket.instructions.md

ai-instructions spring-boot-websocket.instructions.md is an instructions file for GitHub Copilot from lsampaioweb/ai-instructions. It costs 927 tokens per session, scanned A, original, MIT.

A set of coding rules for Spring Boot WebSocket applications that use STOMP, a messaging protocol for sending messages between browsers and servers.

In plain words
What is it for?
Use it when building or reviewing real-time features such as live updates, chat, notifications, or point-to-point messaging in a Spring Boot application.
Why use it?
It keeps message paths, connection authentication, browser fallbacks, heartbeats, and allowed origins consistent. This reduces connection failures and accidental security gaps.

Instructions file for GitHub Copilot

Written for GitHub Copilot: a Copilot instructions file.

This is lsampaioweb/ai-instructions's own configuration. It tells GitHub Copilot how to work on ai-instructions itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything ai-instructions configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/lsampaioweb/ai-instructions/main/.github/instructions/spring-boot-websocket.instructions.md
Clone the repo
git clone --depth 1 https://github.com/lsampaioweb/ai-instructions

Made for: GitHub Copilot.

Wrote 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.

agentmods badge for ai-instructions spring-boot-websocket.instructions.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/lsampaioweb/ai-instructions/spring-boot-websocket/github.svg)](https://agentmods.dev/instructions/lsampaioweb/ai-instructions/spring-boot-websocket)
Your own site
<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/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.

agentmods 80×15 button for ai-instructions spring-boot-websocket.instructions.md

Your own site · 80×15
<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="Reviewed on agentmods" width="80" height="20"></a>
Per session 927 This file is loaded in full into every session.
When invoked 927 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00927 $0.00927
Opus 5.5 $0.00371 $0.00371
Sonnet 5.5 $0.00185 $0.00185
Haiku 4.5 $0.00093 $0.00093

Measured 1mo ago against content hash 9515abc8f3fa, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 1mo 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.

.github/instructions/spring-boot-websocket.instructions.md · 92 lines

How it starts

The opening of the file, as written. The whole thing — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Spring Boot WebSocket Contract

These rules apply when an application uses WebSocket/STOMP messaging. Architecture owns <Feature>SocketController naming. REST JSON APIs stay in the controller contract. Thymeleaf owns browser page UI. HTTP Security stays in the Security contract; do not invent a partial STOMP-auth story here unless the product explicitly requires it.

Applications that expose WebSocket/STOMP must meet this contract.

Dependency and protocol

  • Add spring-boot-starter-websocket when the application needs real-time bidirectional messaging.
  • Prefer STOMP over WebSocket for application messaging (chat, live updates, push notifications).
  • Do not introduce raw JSR-356 @ServerEndpoint handlers unless the product explicitly requires them.
  • Keep a one-line purpose comment above the dependency (pom contract).

Endpoint and destinations

  • Register a STOMP endpoint (commonly /ws).
  • Enable SockJS on that endpoint when browser clients need transport fallback (withSockJS()).
  • Use /app as the application destination prefix for client → server sends.
  • Use a simple broker with /topic for broadcasts (and /queue when point-to-point destinations are required).
  • Prefer the simple in-memory broker for single-instance apps. Do not add an external STOMP broker unless the product needs multi-instance fan-out.

Controllers and flow

  • Name STOMP message handlers <Feature>SocketController and annotate them with @Controller (architecture contract).
  • Keep socket controllers thin: accept the payload, call a service interface, return or route the result. Do not put business rules in the socket controller.
  • Use @MessageMapping for inbound application destinations and @SendTo (or messaging templates) for broadcasts.
  • Optional HTTP status endpoints related to the same feature use normal REST naming (<Feature>RestController), not *SocketController.

Allowed origins (CORS)

  • Bind allowed origins through validated @ConfigurationProperties (for example app.websocket.allowed-origins).
  • Never commit * as an allowed origin in shared/base or production configuration.
  • In application-development.yml, list explicit local origins (scheme, host, and port), such as the browser client origin.
  • In application-production.yml, load concrete origins from environment variables or an external secret/config source (configuration contract).
  • If the resolved origin list is empty, fail closed: do not fall back to *. Refuse to start or refuse to register the STOMP endpoint until origins are configured.
  • Prefer setAllowedOriginPatterns with the configured list over deprecated APIs when configuring the endpoint.

Read the full file on GitHub · 92 lines

Changes

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.

  1. 1mo ago Changed · +4 lines · +70 tokens per session 9515abc8f3fa
  2. 1mo ago Changed · +9 lines · -401 tokens per session 01f0adbd5f13
  3. 1mo ago Changed · +47 lines · +866 tokens per session f904788daf1b
  4. 2mo ago First seen · 32 lines · 392 tokens per session scan A ef85a8542c62

Subscribe to this mod's changes

ai-instructions spring-boot-websocket.instructions.md is an instructions file published in the GitHub repository lsampaioweb/ai-instructions (1 stars, last pushed 5d ago), licensed MIT. It adds 927 tokens to every session, about $0.0037 per session on Opus 5.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.

Related

ai-instructions spring-boot-websocket.instructions.md compared with instructions from other repositories

ai-instructions spring-boot-websocket.instructions.md next to 6 instructions from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
ai-instructions spring-boot-websocket.instructions.mdlsampaioweb/ai-instructionsInstructions file15d agoMITA927GitHub Copilot
vscode buildNext.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA9,719GitHub Copilot
next.js AGENTS.mdvercel/next.jsInstructions file143ktodayMITA7,461Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchainInstructions file149kyesterdayMITA4,680Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA5,516GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA3,093GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harnessInstructions file274k2d agoMITA4,313Codex, OpenCode