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.
git 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/rules/lsampaioweb/ai-instructions/spring-boot-traefik)<a href="https://agentmods.dev/rules/lsampaioweb/ai-instructions/spring-boot-traefik"><img src="https://agentmods.dev/badge/rules/lsampaioweb/ai-instructions/spring-boot-traefik/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.
<a href="https://agentmods.dev/rules/lsampaioweb/ai-instructions/spring-boot-traefik"><img src="https://agentmods.dev/badge/rules/lsampaioweb/ai-instructions/spring-boot-traefik.svg" alt="Reviewed on agentmods" width="80" 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.00000 | $0.00565 |
| Opus 5.5 | $0.00000 | $0.00226 |
| Sonnet 5.5 | $0.00000 | $0.00113 |
| Haiku 4.5 | $0.00000 | $0.00056 |
Grade A, and why
spring-boot-traefik 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 14d 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.
How it starts
The opening of the file, as written. The whole thing — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spring Boot Traefik Contract
Apply this contract when a Spring Boot app (or HTTP sidecar UI) is routed through Traefik. Traefik proxy Compose, dashboard, sockets, and cert files stay in the infrastructure runbook for the environment.
Container owns image build, resources, healthchecks, profiles, and generic networks. TLS owns application keystores when the app terminates TLS itself. Actuator and security own health exposure and actuator credentials.
App Compose routing
- Join the shared external Docker network used by Traefik and the apps it routes.
- Enable Traefik on the service with
traefik.enable=true. - Route with an explicit Host rule (for example
Host(\app.example.com`)`). Changing a Traefik domain env var does not rewrite these labels — edit the Host rule when the suffix changes. - Set
traefik.http.services.<name>.loadbalancer.server.portto the container listen port (aligned with the active Spring profile /SERVER_PORT). - Default entrypoint is
web. For Traefik HTTPS termination, switch towebsecureandtls=truetogether. - Keep Traefik → app traffic HTTP on that loadbalancer port. Do not point Traefik at an HTTPS-only app listener unless the deployment explicitly terminates TLS in the app (container TLS-boundary rule).
Traefik-only ingress
When Compose intends Traefik as the only ingress:
- Do not publish app
ports:on the host; Traefik is the entrypath. - Keep the Host rule, enable flag, loadbalancer port, and shared-network declarations present and consistent.
Optional service labels
- HTTP UIs on other infra services may use the same label pattern. Non-HTTP protocols stay on their native ports and are not Traefik-routed.
Forbidden
- Never expect Traefik to discover an app that is off the shared Traefik network
or missing
traefik.enable=true. - Never publish host
ports:for an app that claims Traefik-only ingress. - Never leave Host labels on an old domain after changing the DNS suffix without updating those labels.
- Never point
loadbalancer.server.portat a different port than the process actually listens on inside the container.
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.
- 14d ago First seen · 54 lines · 0 tokens per session scan A fda1d9dea434
spring-boot-traefik is a cursor rule published in the GitHub repository lsampaioweb/ai-instructions (1 stars, last pushed 14d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 565 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-10-04.
Other cursor rules, from other repositories
python-containerization-cursorrules-prompt-file
Cursor rules for Python development with containerization integration.
aws-ecs
Definitive guidelines for building, deploying, and operating applications on AWS ECS, emphasizing immutable containers, secure secrets management, and robust operational patterns.
hack
Hack is local-first. This project uses hack for local runtime orchestration (compose + DNS/TLS + logs + sessions). Prefer hack when shell access is available. Use MCP only when shell access is unavailable.
local-compose-db-lifecycle-for-web-tests
Keep local compose DB lifecycle ready for web tests.
runwhen-infrastructure
Infrastructure conventions for scripts targeting Kubernetes and databases via RunWhen runners.
container-rightsizer
Rightsizes container CPU and memory requests and limits using real usage data. Reduces requested resources without hitting OOMKills or CPU throttling.