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-tracing)<a href="https://agentmods.dev/rules/lsampaioweb/ai-instructions/spring-boot-tracing"><img src="https://agentmods.dev/badge/rules/lsampaioweb/ai-instructions/spring-boot-tracing/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-tracing"><img src="https://agentmods.dev/badge/rules/lsampaioweb/ai-instructions/spring-boot-tracing.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.00568 |
| Opus 5.5 | $0.00000 | $0.00227 |
| Sonnet 5.5 | $0.00000 | $0.00114 |
| Haiku 4.5 | $0.00000 | $0.00057 |
Grade A, and why
spring-boot-tracing 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spring Boot Tracing Contract
Apply this contract when a module adds distributed tracing with Micrometer Tracing and OpenTelemetry. It does not replace the logging, actuator, controller, or pom contracts.
Stack
- Use Spring Boot's OpenTelemetry support via
spring-boot-starter-opentelemetry. - Prefer Micrometer Tracing with the OpenTelemetry bridge. Do not add Brave / Zipkin unless the user explicitly asks for that stack.
- Export traces with OTLP to a Collector (or compatible backend). Do not invent a custom HTTP exporter.
Configuration
- Set
management.tracing.sampling.probabilityto1.0for local demos so every request produces spans. Use a lower probability in production when volume or cost requires it, and document why. - Configure OTLP with
management.opentelemetry.tracing.export.otlp.endpoint(HTTP protobuf default), pointing at the Collector (for examplehttp://localhost:4318/v1/traces). - Disable OTLP metrics export (
management.otlp.metrics.export.enabled=false) when the Collector pipeline is traces-only, so demos do not spam failed/v1/metricsposts. - Disable OTLP export in
application-test.ymlso context tests do not require a running Collector. - Give each traced service a distinct
spring.application.name.
Propagation and HTTP clients
- Build outbound
RestClientinstances from the auto-configuredRestClient.Builder(requiresspring-boot-starter-restclient) so observation and W3C trace context propagate automatically. - Do not manually set
traceparentheaders in application code for ordinary HTTP calls when Boot instrumentation covers the client.
Log correlation
- When a module enables Micrometer Tracing, include MDC
traceIdandspanIdin that module's Logback console and file patterns. - Do not add correlation IDs to modules that do not depend on tracing.
Forbidden
- Never use Brave as the default tracing bridge when OpenTelemetry was requested.
- Never require a trace UI (Jaeger, Tempo, Grafana) for a Collector-only setup.
- Never hardcode sampling below
1.0in local demos without documenting why. - Never create a custom
RestClient.builder()for traced calls when the observed auto-configuredRestClient.Builderbean is available.
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 · 56 lines · 0 tokens per session scan A d5e574fd8116
spring-boot-tracing 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 568 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
mcp-debugging
The mcp-debug agent provides essential tools to test and explore MCP (Model Context Protocol) servers. This guide focuses on using the agent to debug MCP server behavior and functionality.
error-handling-pattern-3-custom-error-strategies
Cursor rule "error-handling-pattern-3-custom-error-strategies" from PaulJPhilp/EffectPatterns, covering error handling pattern 3: custom error strategies and example.
fastapi-middleware
A small set of FastAPI rules covering expected errors, middleware, logging, error monitoring, and Pydantic models for checking request and response data.
seam-audit
A method for finding interface-seam bugs, where two connected parts of a system do not actually pass information between each other. It checks UI, events, fields, routes, database columns, producers, and consumers, while distinguishing real gaps from intentional omissions.
error-handling
Error handling patterns for backend services. Apply when handling errors in handlers or services.
Error Handling and Logging
All application errors go through the centralized hierarchy in back/core/errors/. A global exception handler in shared/fastapi/main.createapp() translates them into a uniform ErrorResponse JSON body.