Use it to configure API authentication, page authentication, role checks, permission components, and protected request paths.

It reduces the risk of accidentally exposing endpoints or allowing unsafe operations without authorization.

How lsampaioweb/ai-instructions configures GitHub Copilot

Q: What is ai-instructions spring-boot-security.instructions.md?

A set of Spring Boot rules for protecting web applications and REST APIs. It covers sign-in, permissions, tokens, sessions, and default handling for routes that are not explicitly allowed.

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

README.md

[![agentmods](https://agentmods.dev/badge/instructions/lsampaioweb/ai-instructions/spring-boot-security/github.svg)](https://agentmods.dev/instructions/lsampaioweb/ai-instructions/spring-boot-security)

Your own site

<a href="https://agentmods.dev/instructions/lsampaioweb/ai-instructions/spring-boot-security"><img src="https://agentmods.dev/badge/instructions/lsampaioweb/ai-instructions/spring-boot-security/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/lsampaioweb/ai-instructions/spring-boot-security"><img src="https://agentmods.dev/badge/instructions/lsampaioweb/ai-instructions/spring-boot-security.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 1,006 This file is loaded in full into every session.

When invoked 1,006 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.

Model	Per session	Once invoked
Fable 5.1	$0.01006	$0.01006
Opus 5.5	$0.00402	$0.00402
Sonnet 5.5	$0.00201	$0.00201
Haiku 4.5	$0.00101	$0.00101

Measured 1mo ago against content hash 6a74877a2890, 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-security.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-security.instructions.md · 100 lines

How it starts

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

Spring Boot Security Contract

These rules apply when an application uses Spring Security. Actuator exposure and the health-anonymous / other-actuator-authenticated boundary stay in the Actuator contract. Secrets policy stays in the configuration contract. Do not restate those contracts here.

An application that exposes private APIs or non-health Actuator endpoints must meet this contract.

The default auth model is HTTP Basic with in-memory principals loaded from environment variables. A later, more advanced pattern may introduce database-backed credentials; do not invent that stack unless the product explicitly requires it.

Dependency

Add spring-boot-starter-security when the application has anything that must not be anonymous.
Add spring-security-test with test scope when writing security tests.
Keep a one-line purpose comment above each dependency (pom contract).

Authentication mechanism

Use HTTP Basic for REST/API and machine-to-machine callers.
Do not add form login unless the application is a browser form/MVC app and the product explicitly needs it.
Do not add OAuth2/JWT resource-server or client stacks unless the product explicitly requires them.

Filter chain

Configure exactly the SecurityFilterChain beans the application needs; do not rely on Spring Boot's default wide-open or default-user behavior for production APIs.
Deny by default: after explicit public and authenticated rules, end with anyRequest().denyAll().
Permit only routes that must be anonymous (for example a documented public health-check style API path, or OpenAPI/Swagger when enabled in development).
Require authentication or a role for every private API route.
For pure HTTP Basic REST APIs, set SessionCreationPolicy.STATELESS and disable CSRF. Keep CSRF enabled for browser form/MVC apps.
Prefer @EnableMethodSecurity and put sensitive authorization checks on service methods with @PreAuthorize (or equivalent), in addition to URL rules (architecture contract: authorization that belongs to the application service).

Read the full file on GitHub · 100 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.

1mo ago Changed · +5 lines · -426 tokens per session 6a74877a2890
1mo ago Changed · +39 lines · +686 tokens per session 31682a30c248
2mo ago First seen · 56 lines · 746 tokens per session scan A 45af3f0a3881

Subscribe to this mod's changes

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

Backend and APIs Security

ai-instructions spring-boot-security.instructions.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
ai-instructions spring-boot-security.instructions.mdlsampaioweb/ai-instructions	Instructions file	1	5d ago	MIT	A	1,006	GitHub Copilot
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	today	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	yesterday	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

ai-instructions: Instructions file for GitHub Copilot