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.
npx agentmods add rules/getsentry/sentry-java/offlinegit 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/offline)<a href="https://agentmods.dev/rules/getsentry/sentry-java/offline"><img src="https://agentmods.dev/badge/rules/getsentry/sentry-java/offline.svg" alt="Measured on agentmods" 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 | $0.00004 | $0.01092 |
| Opus 5 | $0.00002 | $0.00546 |
| Sonnet 5 | $0.00001 | $0.00218 |
| Haiku 4.5 | $0.00000 | $0.00109 |
Grade A, and why
offline 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 yesterday.
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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Java SDK Offline behaviour
By default offline caching is enabled for Android but disabled for JVM. It can be enabled by setting SentryOptions.cacheDirPath.
For Android, AndroidEnvelopeCache is used. For JVM, if cache path has been configured, EnvelopeCache will be used.
Any error, event, transaction, profile, replay etc. is turned into an envelope and then sent into ITransport.send. The default implementation is AsyncHttpTransport.
If an envelope is dropped due to rate limit and has previously been cached (Cached hint) it will be discarded from the IEnvelopeCache.
AsyncHttpTransport.send will enqueue an AsyncHttpTransport.EnvelopeSender task onto an executor.
Any envelope that doesn't have the Cached hint will be stored in IEnvelopeCache by the EventSender task. Previously cached envelopes (Cached hint) will have a noop cache passed to AsyncHttpTransport.EnvelopeSender and thus not cache again. It is also possible cache is disabled in general.
An envelope being sent directly from SDK API like Sentry.captureException will not have the Retryable hint.
In case the SDK is offline, it'll mark the envelope to be retried if it has the Retryable hint. If the envelope is not retryable and hasn't been sent to offline cache, it's recorded as lost in a client report.
In case the envelope can't be sent due to an error or network connection problems it'll be marked for retry if it has the Retryable hint. If it's not retryable and hasn't been cached, it's recorded as lost in a client report.
In case the envelope is sent successfully, it'll be discarded from cache.
The SDK has multiple mechanisms to deal with envelopes on disk.
- OutboxSender: Sends events coming from other SDKs like NDK that wrote them to disk.
- io.sentry.EnvelopeSender: This is the offline cache.
Both of these are set up through an integration (SendCachedEnvelopeIntegration) which is configured to use SendFireAndForgetOutboxSender or SendFireAndForgetEnvelopeSender.
io.sentry.EnvelopeSender is able to pick up files in the cache directory and send them. It will trigger sending envelopes in cache dir on init and when the connection status changes (e.g. the SDK comes back online, meaning it has Internet connection again).
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.
- yesterday First seen · 88 lines · 4 tokens per session scan A c0c6bb0bc778
offline is a cursor rule published in the GitHub repository getsentry/sentry-java (1,349 stars, last pushed today), licensed MIT. It adds 4 tokens to every session and 1,092 once invoked, about $0.0000 per session on Opus 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
android-viewmodel
Android ViewModel conventions — StateFlow, repository abstraction, coroutines, no LiveData.
swiftui-accessibility
SwiftUI accessibility rules for VoiceOver — labels, hints, traits, values, and attribute preservation.
project-status
PriceGrab shipped state and product backlog (read first).
security-threat-and-stability
Maximum security scrutiny on issues/PRs and stability-first code changes.
best-practices
Engineering best practices for this codebase.
android-gradle-build-logic
Shape Android build logic with Gradle, version catalogs, plugins, convention patterns, and toolchain compatibility.