spring-boot-actuator

spring-boot-actuator is a cursor rule for Cursor from lsampaioweb/ai-instructions. It costs 0 tokens per session (635 once invoked), scanned A, original, MIT.

A set of rules for configuring Spring Boot Actuator, the Spring feature used to expose application health, information, metrics, and monitoring endpoints.

In plain words
What is it for?
Use it to configure actuator endpoint access, health details, liveness and readiness probes, metrics, tracing, sampling, and sensitive-data boundaries.
Why use it?
It limits which operational data is exposed and defines safer health checks for applications running in containers.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

Good fit Use it to configure actuator endpoint access, health details, liveness and readiness probes, metrics, tracing, sampling, and sensitive-data boundaries.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/lsampaioweb/ai-instructions/spring-boot-actuator
Install

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.

Clone the repo
git clone --depth 1 https://github.com/lsampaioweb/ai-instructions

Made for: Cursor.

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 spring-boot-actuator

README.md
[![agentmods](https://agentmods.dev/badge/rules/lsampaioweb/ai-instructions/spring-boot-actuator/github.svg)](https://agentmods.dev/rules/lsampaioweb/ai-instructions/spring-boot-actuator)
Your own site
<a href="https://agentmods.dev/rules/lsampaioweb/ai-instructions/spring-boot-actuator"><img src="https://agentmods.dev/badge/rules/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.

agentmods 80×15 button for spring-boot-actuator

Your own site · 80×15
<a href="https://agentmods.dev/rules/lsampaioweb/ai-instructions/spring-boot-actuator"><img src="https://agentmods.dev/badge/rules/lsampaioweb/ai-instructions/spring-boot-actuator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 635 The whole file, excluding the scripts and references it only reads on demand.
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.00000 $0.00635
Opus 5.5 $0.00000 $0.00254
Sonnet 5.5 $0.00000 $0.00127
Haiku 4.5 $0.00000 $0.00064

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

Security

Grade A, and why

spring-boot-actuator 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.

.cursor/rules/spring-boot-actuator.mdc · 77 lines

How it starts

The opening of the file, as written. The whole thing — 77 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 · 77 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 · +29 lines ad7f1b96826e
  2. 2mo ago First seen · 48 lines · 0 tokens per session scan A a64bfd051a27

Subscribe to this mod's changes

spring-boot-actuator is a cursor rule published in the GitHub repository lsampaioweb/ai-instructions (1 stars, last pushed 10d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 635 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.

Related

spring-boot-actuator compared with cursor rules from other repositories

spring-boot-actuator next to 6 cursor rules from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
spring-boot-actuatorlsampaioweb/ai-instructionsCursor rule110d agoMITA0Cursor
ponytailDietrichGebert/ponytailCursor rule193k20d agoMITA604Cursor
angular-20angular/angularCursor rule102ktodayMITA0Cursor
dev-standardapache/supersetCursor rule76ktodayApache-2.0A1,147Cursor
prefer-assertions-over-defensive-checksprisma/ormCursor rule48ktodayApache-2.0A0Cursor
prefer-direct-imports-over-module-mocksprisma/ormCursor rule48ktodayApache-2.0A0Cursor
shared-plane-packagesprisma/ormCursor rule48ktodayApache-2.0A0Cursor