It is for setting safe endpoint access, container health probes, metrics, tracing, sampling, and information shown by the application.

It helps keep diagnostic endpoints limited and prevents health data, metrics, traces, or sensitive details from being exposed accidentally.

How lsampaioweb/ai-instructions configures GitHub Copilot

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

A set of rules for configuring Spring Boot Actuator, the part of Spring Boot that exposes application health and monitoring information.

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-actuator.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-actuator/github.svg)](https://agentmods.dev/instructions/lsampaioweb/ai-instructions/spring-boot-actuator)

Your own site

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

Per session 630 This file is loaded in full into every session.

When invoked 630 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.00630	$0.00630
Opus 5.5	$0.00252	$0.00252
Sonnet 5.5	$0.00126	$0.00126
Haiku 4.5	$0.00063	$0.00063

Measured 1mo ago against content hash d5829f493a04, 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-actuator.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-actuator.instructions.md · 76 lines

How it starts

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

Spring Boot Actuator Contract

These rules apply to applications that ship Spring Boot Actuator. Profile file layout and DevTools stay in the configuration contract. Full HTTP security filter chains stay in the Security topic; this file only states the Actuator exposure and access boundary.

Dependency

Add spring-boot-starter-actuator to every real application module.
Keep a one-line purpose comment above the dependency (pom contract).

Web exposure

Expose only a whitelist under management.endpoints.web.exposure.include.
Default include: health,info,metrics.
Keep the default base path /actuator. Do not invent a custom base path unless the product explicitly requires it.
Never set include: "*".
Do not expose sensitive endpoints by default (env, beans, configprops, heapdump, threaddump, logfile, shutdown, and similar). Add them only with an explicit product need and authentication.

Health details by profile

In application.yml, set management.endpoint.health.show-details to when-authorized.
In application-development.yml, set show-details to always.
In application-production.yml, set show-details to never.

Probes

For real applications that run in containers or orchestrators, enable Kubernetes-style probes:
```
management:
  endpoint:
    health:
      probes:
        enabled: true
```
Keep probe enablement in application.yml (shared), not only in one profile, when the app is meant to be containerized.

Custom health

Add a custom HealthIndicator only when a real dependency must gate readiness (database, broker, remote system). Do not invent vanity indicators.

Access boundary

Anonymous callers may reach /actuator/health and health probe routes only.
Every other /actuator/** path requires authentication.
An allow or authenticate rule for an exposed Actuator endpoint covers that endpoint and the subpaths it serves.
When Spring Security is present in production, prefer a separate management.server.port so management traffic is not mixed with the public API port.
Do not put Actuator credentials in YAML (configuration contract for secrets).

Read the full file on GitHub · 76 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 · +7 lines · -309 tokens per session d5829f493a04
1mo ago Changed · +21 lines · +218 tokens per session ca73bb7624a0
2mo ago First seen · 48 lines · 721 tokens per session scan A 228dd6e32978

Subscribe to this mod's changes

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

ai-instructions spring-boot-actuator.instructions.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
ai-instructions spring-boot-actuator.instructions.mdlsampaioweb/ai-instructions	Instructions file	1	5d ago	MIT	A	630	GitHub Copilot
plan-forge dapr.instructions.mdsrnichols/plan-forge	Instructions file	6	2d ago	MIT	A	4,975	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

ai-instructions: Instructions file for GitHub Copilot