getsentry/sentry-java is a Java and Android software development kit for sending application errors, events, and diagnostic information to Sentry. It is used by developers working with Java, Android, Kotlin, and other JVM-based applications to monitor software behavior. The catalogue rules, skills, instructions, and setting support workflows around this SDK.
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/getsentry/sentry-javaWrote 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/getsentry/sentry-java/opentelemetry)<a href="https://agentmods.dev/rules/getsentry/sentry-java/opentelemetry"><img src="https://agentmods.dev/badge/rules/getsentry/sentry-java/opentelemetry/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/getsentry/sentry-java/opentelemetry"><img src="https://agentmods.dev/badge/rules/getsentry/sentry-java/opentelemetry.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.00005 | $0.01905 |
| Opus 5.5 | $0.00002 | $0.00762 |
| Sonnet 5.5 | $0.00001 | $0.00381 |
| Haiku 4.5 | $0.00001 | $0.00191 |
Grade A, and why
opentelemetry 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.
How it starts
The opening of the file, as written. The whole thing — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Java SDK OpenTelemetry Integration
Overview
The Sentry Java SDK provides comprehensive OpenTelemetry integration through multiple modules:
sentry-opentelemetry-core: Core OpenTelemetry integration functionalitysentry-opentelemetry-agent: Java Agent-based integration for automatic instrumentationsentry-opentelemetry-agentless: Manual instrumentation without Java agentsentry-opentelemetry-agentless-spring: Spring-specific agentless integrationsentry-opentelemetry-bootstrap: Classes that go into the bootstrap classloader when the agent is used. For agentless they are simply used in the applications classloader.sentry-opentelemetry-agentcustomization: Classes that help wire up Sentry in OpenTelemetry. These land in the agent classloader when the agent is used. For agentless they are simply used in the application classloader.sentry-opentelemetry-otlp: Classes for using OpenTelemetry to send spans to Sentry using the OTLP endpoint and have Sentry use OpenTelemetry trace and span id.sentry-opentelemetry-otlp-spring: Spring Boot convenience module that includessentry-opentelemetry-otlpand the OpenTelemetry Spring Boot starter as transitive dependencies.
Advantages over using Sentry without OpenTelemetry
- Support for more libraries and frameworks
- See https://github.com/open-telemetry/opentelemetry-java-instrumentation/tree/main/instrumentation for a list of supported libraries and frameworks
- More automated Performance instrumentation (spans) created
- Using
sentry-opentelemetry-agentoffers most support - Using
sentry-opentelemetry-agentless-springfor Spring Boot also has a lot of supported libraries, altough fewer than the agent does - Note that
sentry-opentelemetry-agentlesswill not have any OpenTelemetry auto instrumentation
- Using
- Sentry also relies on OpenTelemetry
Contextpropagation to propagate SentryScopes, ensuring e.g. that execution flow for a request shares data and does not leak data into other requests. - OpenTelemetry also offers better support for distributed tracing since more libraries are supported for attaching tracing information to outgoing requests and picking up incoming tracing information.
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 First seen · 98 lines · 5 tokens per session scan A e68c32a30cfa
opentelemetry is a cursor rule published in the GitHub repository getsentry/sentry-java (1,357 stars, last pushed today), licensed MIT. It adds 5 tokens to every session and 1,905 once invoked, about $0.0000 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.
Other cursor rules, from other repositories
always-on
Spec-driven Spring Boot 4 — global guardrails that compensate for Windsurf's lack of a pre-tool-use hook.
production-code
Production code rule — TDD precondition + Spring Boot 4 conventions.
test-code
Test code rule — JUnit 5, Testcontainers, traceability tagging.
specs-artifacts
Spec artifact rule — no invention, stable IDs, phase ordering.
backend-java-ruoyi-conventions
YiSmartCloud backend Java RuoYi conventions.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.