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/metricsgit 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/metrics)<a href="https://agentmods.dev/rules/getsentry/sentry-java/metrics"><img src="https://agentmods.dev/badge/rules/getsentry/sentry-java/metrics.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.00002 | $0.00329 |
| Opus 5 | $0.00001 | $0.00164 |
| Sonnet 5 | $0.00000 | $0.00066 |
| Haiku 4.5 | $0.00000 | $0.00033 |
Grade A, and why
metrics 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 today.
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.
What it actually says
Java SDK Metrics API
Metrics are enabled by default.
API has been namespaced under Sentry.metrics() and IScopes.metrics() using the IMetricsApi interface and MetricsApi implementation.
Options are namespaced under SentryOptions.getMetrics().
Three different APIs exist:
count: Counters are one of the more basic types of metrics and can be used to count certain event occurrences.distribution: Distributions help you get the most insights from your data by allowing you to obtain aggregations such as p90, min, max, and avg.gauge: Gauges let you obtain aggregates like min, max, avg, sum, and count. They can be represented in a more space-efficient way than distributions, but they can't be used to get percentiles. If percentiles aren't important to you, we recommend using gauges.
Refer to SentryMetricsEvent for details about available fields.
MetricsBatchProcessor handles batching (MAX_BATCH_SIZE), automatic sending of metrics after a timeout (FLUSH_AFTER_MS) and rejecting if MAX_QUEUE_SIZE has been hit.
The flow is IMetricsApi -> IMetricsBatchProcessor -> SentryClient.captureBatchedMetricsEvents -> ITransport.
Each SentryMetricsEvent goes through SentryOptions.metrics.beforeSend (if configured) and can be modified or dropped.
For sending, a batch of SentryMetricsEvent objects is sent inside a SentryMetricsEvents object.
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.
- today First seen · 27 lines · 2 tokens per session scan A 2496890ba499
metrics is a cursor rule published in the GitHub repository getsentry/sentry-java (1,349 stars, last pushed today), licensed MIT. It adds 2 tokens to every session and 329 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
backend-java-ruoyi-conventions
YiSmartCloud backend Java RuoYi conventions.
component-parameter-key-no-dot
@ComponentParameter 的 key 禁止包含 "."，统一使用下划线 / 顶层扁平命名.
com-example-service-PublicPaymentController
AI rules for com.example.service.PublicPaymentController.
java-springboot-jpa-cursorrules-prompt-file
description: "Cursor rules for Java development with Springboot and JPA integration." globs: / alwaysApply: false.
commit-sponsors
Every git commit message must acknowledge BetterDesk supporters.
security-threat-and-stability
Maximum security scrutiny on issues/PRs and stability-first code changes.