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 skills/getsentry/sentry-java/testnpx skills add getsentry/sentry-java --skill testgit 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/skills/getsentry/sentry-java/test)<a href="https://agentmods.dev/skills/getsentry/sentry-java/test"><img src="https://agentmods.dev/badge/skills/getsentry/sentry-java/test.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.00058 | $0.00861 |
| Opus 5 | $0.00029 | $0.00430 |
| Sonnet 5 | $0.00012 | $0.00172 |
| Haiku 4.5 | $0.00006 | $0.00086 |
Grade A, and why
test 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Run Tests
Run tests for a specific module. Auto-detects whether to run unit tests or system tests.
Step 0: Check for Interactive Mode
If $ARGUMENTS starts with interactive (e.g., /test interactive sentry ScopesTest), enable interactive mode. Strip the interactive keyword from the arguments before proceeding.
In interactive mode, use AskUserQuestion at decision points as described in the steps below.
Step 1: Parse the Argument
The argument can be either:
- A file path (e.g.,
@sentry/src/test/java/io/sentry/ScopesTest.kt) - A module name (e.g.,
sentry-android-core,sentry-samples-spring-boot-4) - A module name + test filter (e.g.,
sentry ScopesTest)
Extract the module name and optional test class filter from the argument.
Interactive mode: If the test filter is ambiguous (e.g., matches multiple test classes across modules), use AskUserQuestion to let the user pick which test class(es) to run.
Step 2: Detect Test Type
| Signal | Test Type |
|---|---|
Path contains sentry-samples/ |
System test |
Module name starts with sentry-samples- |
System test |
| Everything else | Unit test |
Step 3a: Run Unit Tests
Determine the Gradle test task:
| Module Pattern | Test Task |
|---|---|
sentry-android-* |
testReleaseUnitTest |
sentry-compose* |
testReleaseUnitTest |
*-android |
testReleaseUnitTest |
| Everything else | test |
Interactive mode: Before running, read the test class file and use AskUserQuestion to ask:
- "Run all tests in this class, or a specific method?" — list the test method names as options.
If the user picks a specific method, use --tests="*ClassName.methodName" as the filter.
With a test class filter:
./gradlew ':<module>:<task>' --tests="*<filter>*" --info
Without a filter:
./gradlew ':<module>:<task>' --info
Step 3b: Run System Tests
System tests require the Python-based test runner which manages a mock Sentry server and sample app lifecycle.
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 · 94 lines · 0 tokens per session scan A 8b66210014eb
test is a skill published in the GitHub repository getsentry/sentry-java (1,349 stars, last pushed today), licensed MIT. It adds 58 tokens to every session and 861 once invoked, about $0.0003 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 skills, from other repositories
test-flutter
Flutter App のテスト実行・静的解析・フォーマット・テスト記述ガイド.
verify-work
Verify feature, bug, UI, API, mobile, security, or deployment work against acceptance criteria.
ios-testing
Testing patterns for Swift and SwiftUI apps.
mobile-testing
Android and JVM testing - JUnit5, MockK, Turbine for Flow, and Compose UI testing for unit, integration, and UI tests; also applies to KMP commonTest running on the JVM/Android target. For iOS/Swift tests (XCTest, Swift Testing, XCUITest) use ios-testing. For TDD methodology and the three-tier test model (fake-first…
android-kotlin-testing
Android testing patterns — ViewModel unit tests with Turbine, Compose UI semantics, Hilt TestInstallIn fakes, coroutine test dispatchers, and release quality gates. Use when writing tests, setting up CI, mocking repositories, or asking "how to test ViewModel", "Compose UI test", "Turbine StateFlow".
flutter-testing
Flutter + NestJS 多区域项目测试规范 — Flutter 单元测试（Notifier/Provider + ProviderContainer override）、widget 测试、golden 测试、★ flavor 条件编译测试（cn 不含 Firebase / overseas 不含 JPush 的静态与运行时验证）、多租户隔离测试、AI 扣费 refund 测试、NestJS service 单测（mock Prisma）、e2e（supertest + 测试库）、mocktail/jest mock 约定、覆盖率门禁。.