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/continuous_profiling_jvmgit 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/continuous_profiling_jvm)<a href="https://agentmods.dev/rules/getsentry/sentry-java/continuous_profiling_jvm"><img src="https://agentmods.dev/badge/rules/getsentry/sentry-java/continuous_profiling_jvm.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.00013 | $0.01846 |
| Opus 5 | $0.00006 | $0.00923 |
| Sonnet 5 | $0.00003 | $0.00369 |
| Haiku 4.5 | $0.00001 | $0.00185 |
Grade A, and why
continuous_profiling_jvm 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.
How it starts
The opening of the file, as written. The whole thing — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
JVM Continuous Profiling
Use this rule when working on JVM continuous profiling in sentry-async-profiler and the related core profiling abstractions in sentry.
This area is suitable for LLM work, but do not rely on this rule alone for behavior changes. Always read the implementation and nearby tests first, especially for sampling, lifecycle, rate limiting, and file cleanup behavior.
Module Structure
-
sentry-async-profiler: standalone module containing the async-profiler integration- Uses Java
ServiceLoaderdiscovery - No direct dependency from core
sentrymodule - Enabled by adding the module as a dependency
- Uses Java
-
sentrycore abstractions:IContinuousProfiler: profiler lifecycle interfaceProfileChunk: profile chunk payload sent to SentryIProfileConverter: converts JVM JFR files intoSentryProfileProfileLifecycle: controls MANUAL vs TRACE lifecycleProfilingServiceLoader: loads profiler and converter implementations viaServiceLoader
Key Classes
JavaContinuousProfiler (sentry-async-profiler)
- Wraps the native async-profiler library
- Writes JFR files to
profilingTracesDirPath - Rotates chunks periodically via
MAX_CHUNK_DURATION_MILLIS(currently 10s) - Implements
RateLimiter.IRateLimitObserver - Maintains
rootSpanCounterfor TRACE lifecycle - Keeps a session-level
profilerIdacross chunks until the profiling session ends getChunkId()currently returnsSentryId.EMPTY_ID, but emittedProfileChunks get a fresh chunk id when built instop(...)
ProfileChunk
- Carries
profilerId,chunkId, timestamp, platform, measurements, and a JFR file reference - Built via
ProfileChunk.Builder - For JVM, the JFR file is converted later during envelope item creation, not inside
JavaContinuousProfiler
ProfileLifecycle
MANUAL: explicitSentry.startProfiler()/Sentry.stopProfiler()TRACE: profiler lifecycle follows active sampled root spans
Configuration
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 · 175 lines · 13 tokens per session scan A 42a3f0ffccd8
continuous_profiling_jvm is a cursor rule published in the GitHub repository getsentry/sentry-java (1,349 stars, last pushed today), licensed MIT. It adds 13 tokens to every session and 1,846 once invoked, about $0.0001 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.