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/queues)<a href="https://agentmods.dev/rules/getsentry/sentry-java/queues"><img src="https://agentmods.dev/badge/rules/getsentry/sentry-java/queues/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/queues"><img src="https://agentmods.dev/badge/rules/getsentry/sentry-java/queues.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.00010 | $0.01220 |
| Opus 5.5 | $0.00004 | $0.00488 |
| Sonnet 5.5 | $0.00002 | $0.00244 |
| Haiku 4.5 | $0.00001 | $0.00122 |
Grade A, and why
queues 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sentry Queues and Java SDK Queue Tracing
Product model
Sentry Queues is built from tracing data. SDKs mark queue work with queue-specific span operations and messaging span data so Sentry can identify producers, consumers, destinations, latency, and failures.
The important concepts are:
queue.publish: a span for enqueueing/publishing a message to a queue or topic.queue.process: a transaction for processing a dequeued message.- Messaging span data, especially:
messaging.system(for examplekafka)messaging.destination.name(queue/topic name)messaging.message.idmessaging.message.retry.countmessaging.message.body.sizemessaging.message.envelope.sizemessaging.message.receive.latency
- Distributed tracing headers (
sentry-traceandbaggage) link producer-side work to consumer-side processing. - Queue receive latency is the time a message spent waiting between publish/enqueue and processing. For Java Kafka, this comes from the
sentry-task-enqueued-timeheader that the producer writes and the consumer reads.
The Queues UI is not backed by a separate Java event type. The Java SDK contributes data through spans/transactions with the expected operations, trace context, statuses, and messaging attributes.
Java SDK implementation
Queue tracing is opt-in. SentryOptions.isEnableQueueTracing() defaults to false and can be enabled with setEnableQueueTracing(true) or external config key enable-queue-tracing (sentry.enable-queue-tracing in Spring Boot). Captured queue spans/transactions still depend on tracing being enabled and sampled.
Kafka support lives in sentry-kafka:
SentryKafkaProducer.wrap(Producer)wraps KafkaProducer.send(...)calls.- Creates a
queue.publishchild span when there is an active span. - Sets
messaging.system=kafkaandmessaging.destination.name=<topic>. - Injects
sentry-trace,baggage, andsentry-task-enqueued-timeheaders. - Still injects tracing/enqueued-time headers when queue tracing is enabled but there is no active span, so background producers can link to consumers.
- Finishes the span from the Kafka callback with
OKorINTERNAL_ERROR.
- Creates a
SentryKafkaConsumerTracing.withTracing(record, callback)is the manual raw-Kafka consumer helper.- Forks root scopes for the processing lifecycle and makes them current.
- Continues the trace from Kafka headers.
- Starts a
queue.processtransaction bound to scope when tracing is enabled. - Sets Kafka messaging data, body size, retry count, and receive latency when available.
- Finishes with
OKorINTERNAL_ERRORand never lets instrumentation failures break customer processing.
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 · 83 lines · 10 tokens per session scan A 0cff65e1784e
queues is a cursor rule published in the GitHub repository getsentry/sentry-java (1,357 stars, last pushed today), licensed MIT. It adds 10 tokens to every session and 1,220 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.