options

options is a cursor rule for Cursor from getsentry/sentry-java. It costs 5 tokens per session (1,442 once invoked), scanned A, original, MIT.

Guidance for adding or changing configuration options in the Java SDK. It explains how new settings should be structured and why new features normally start disabled until users opt in.

In plain words
What is it for?
Use it when adding settings, callbacks, sampling controls, or feature switches to SentryOptions and related SDK APIs.
Why use it?
It keeps SDK configuration consistent and avoids unexpectedly changing application behavior when a new feature is introduced.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

Good fit Use it when adding settings, callbacks, sampling controls, or feature switches to SentryOptions and related SDK APIs.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/getsentry/sentry-java/options
About the project

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.

getsentry/sentry-java · 1,357 stars · on GitHub · docs.sentry.io

Install

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.

Clone the repo
git clone --depth 1 https://github.com/getsentry/sentry-java

Made for: Cursor.

Wrote 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.

agentmods badge for options

README.md
[![agentmods](https://agentmods.dev/badge/rules/getsentry/sentry-java/options/github.svg)](https://agentmods.dev/rules/getsentry/sentry-java/options)
Your own site
<a href="https://agentmods.dev/rules/getsentry/sentry-java/options"><img src="https://agentmods.dev/badge/rules/getsentry/sentry-java/options/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.

agentmods 80×15 button for options

Your own site · 80×15
<a href="https://agentmods.dev/rules/getsentry/sentry-java/options"><img src="https://agentmods.dev/badge/rules/getsentry/sentry-java/options.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 5 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,442 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00005 $0.01442
Opus 5.5 $0.00002 $0.00577
Sonnet 5.5 $0.00001 $0.00288
Haiku 4.5 $0.00001 $0.00144

Measured 1mo ago against content hash 01109f7332e1, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

options 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.

.cursor/rules/options.mdc · 116 lines

How it starts

The opening of the file, as written. The whole thing — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Adding Options to the SDK

New features must be opt-in by default. Options control whether a feature is enabled and how it behaves.

Namespaced Options

Newer features use namespaced option classes nested inside SentryOptions, e.g.:

  • SentryOptions.getLogs() → SentryOptions.Logs
  • SentryOptions.getMetrics() → SentryOptions.Metrics

Each namespaced options class is a public static final class inside SentryOptions with its own fields, getters/setters, and callbacks (e.g. BeforeSendLogCallback, BeforeSendMetricCallback).

A typical namespaced options class contains:

  • enabled boolean (default false for opt-in)
  • sampleRate double (if the feature supports sampling)
  • beforeSend callback interface (nested inside the options class)

To add a new namespaced options class:

  1. Create the public static final class inside SentryOptions with fields, getters/setters, and any callback interfaces
  2. Add a private field on SentryOptions initialized with new SentryOptions.MyFeature()
  3. Add getter/setter on SentryOptions annotated with @ApiStatus.Experimental

Direct (Non-Namespaced) Options

Options that apply globally across the SDK (e.g. dsn, environment, release, sampleRate, maxBreadcrumbs) live as direct fields on SentryOptions with getter/setter pairs. Use this pattern for options that aren't tied to a specific feature namespace.

Configuration Layers

Options can be set through multiple layers. When adding a new option, consider which layers apply:

1. SentryOptions (always required)

The core options class. Add the field (or nested class) with getter/setter here.

File: sentry/src/main/java/io/sentry/SentryOptions.java

Tests: sentry/src/test/java/io/sentry/SentryOptionsTest.kt

  • Test the default value
  • Test merge behavior (see layer 2)

2. ExternalOptions (sentry.properties / environment variables)

Allows setting options via sentry.properties file or system properties. Fields use nullable wrapper types (@Nullable Boolean, @Nullable Double) since unset means "don't override the default."

Read the full file on GitHub · 116 lines

Changes

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.

  1. 1mo ago First seen · 116 lines · 5 tokens per session scan A 01109f7332e1

Subscribe to this mod's changes

options 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,442 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.