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/check-code-attributionnpx skills add getsentry/sentry-java --skill check-code-attributiongit 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/check-code-attribution)<a href="https://agentmods.dev/skills/getsentry/sentry-java/check-code-attribution"><img src="https://agentmods.dev/badge/skills/getsentry/sentry-java/check-code-attribution.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.00039 | $0.03849 |
| Opus 5 | $0.00019 | $0.01924 |
| Sonnet 5 | $0.00008 | $0.00770 |
| Haiku 4.5 | $0.00004 | $0.00385 |
Grade A, and why
check-code-attribution 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 — 245 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Check Code Attribution
You are reviewing changed files for third-party code attribution compliance in sentry-java, an MIT-licensed repository.
Local runs
When running locally (not via Warden), review every file changed on this branch vs the base branch. Apply the same path exclusions as ignorePaths in warden.toml, then run Quick triage and the checks below on each file. For git commands to list changed files and Warden CLI setup, see validation-tests/README.md. /check-code-attribution in the IDE does not require Warden credentials.
When running via Warden, the changed file is already provided — skip branch-wide discovery, but follow Warden execution below.
Warden execution
Warden analyzes one changed file per run (whole-file mode). Complete every Quick triage step — the diff alone is not sufficient.
Mandatory on every run (do not skip):
- Read the first 50 lines of the changed file.
- Search
THIRD_PARTY_NOTICES.mdfor the class name (filename without extension, e.g.ANRWatchDogforANRWatchDog.java). On renames, also search for the old basename and read Scope sections (see Quick triage). - When you can compare against the base branch version, inspect the header at that revision (first 50 lines).
Do not dismiss findings because:
- A
THIRD_PARTY_NOTICES.mdentry exists — file headers are still required; NOTICES does not replace them. - The diff only removes a header comment block — if removed
-lines include a required field (see below) or vendoring language ("adapted from", etc.), attribution was stripped. Removing boilerplate alone is not stripping. - The header says "Adapted from …" but omits copyright holder or license name — flag missing header fields.
- The file header has all four required fields — a missing THIRD_PARTY_NOTICES.md entry is independently required and is ⚠️ medium regardless of header completeness.
For THIRD_PARTY_NOTICES.md runs: for every removed entry in the diff, confirm whether Scope files still exist with attribution headers. If they do, the entry must not be removed.
What ships with it
13 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- validation-tests/assert-scenarios.mjs 12 KB runs code
- validation-tests/check-code-attribution-tests.sh 8.9 KB runs code
- validation-tests/EXPECTED.json 1.9 KB
- validation-tests/README.md 4.2 KB
- validation-tests/scenarios/HeaderCompleteAndNoticePresent.java 482 B
- validation-tests/scenarios/HeaderCompleteButNoticeMissing.java 307 B
- validation-tests/scenarios/HeaderFullyStripped.java 190 B
- validation-tests/scenarios/HeaderMissingButNoticePresent.java 146 B
- validation-tests/scenarios/HeaderMissingNonEssentialInfo.java 282 B
- validation-tests/scenarios/HeaderPartiallyStripped.java 221 B
- validation-tests/scenarios/NewLicenseType.java 263 B
- validation-tests/scenarios/THIRD_PARTY_NOTICES.mismatch-snippet.md 1.5 KB
- validation-tests/THIRD_PARTY_NOTICES.catalog.md 4.7 KB
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 · 245 lines · 39 tokens per session scan A 3c362a34091b
check-code-attribution is a skill published in the GitHub repository getsentry/sentry-java (1,349 stars, last pushed today), licensed MIT. It adds 39 tokens to every session and 3,849 once invoked, about $0.0002 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
mate-oss-gate
在准备把 MateCloud（或其子集）开源 / 发布到公开仓前使用。按 open-core 边界把关：剥离企业代码、清竞品名与内部路径、查密钥、确认 LICENSE。当用户说"要开源了""发布公开版""开源前检查""oss release"时触发。.
app-store-preflight-compliance
Pre-submission compliance scanner workflow for Apple App Store apps. Use when reviewing iOS, macOS, tvOS, watchOS, or visionOS projects (Swift, Objective-C, React Native, Expo) for App Store rejection risks, submission readiness, privacy compliance, or guideline violations.
app-store-review
Audit an iOS app's App Store submission readiness and rejection risk for a fintech app — App Review Guidelines domains (Safety/Performance/Business/Design/Legal), PrivacyInfo.xcprivacy (NSPrivacyAccessedAPITypes required-reason APIs, NSPrivacyTrackingDomains, NSPrivacyCollectedDataTypes), App Privacy nutrition labels…
gps-compliance
Google Play data safety declarations, app recovery actions, and device tier configs via gps. Use when updating Data safety, creating recovery actions, or managing device tier configuration.
admob-policy
Diagnose and fix any AdMob, Google Publisher, or Google Play ads policy violation in a native Android app — full catalog of Policy Center issues with the concrete code fix for each. Covers Modified ad behavior, accidental clicks, unexpected interstitials, ad density, ads interfering with navigation, inventory value…
ipaship-audit
Use when auditing iOS/Android app submissions for compliance with Apple App Store Review Guidelines or Google Play Developer Policies. Scan .ipa, .apk, or .zip files against official store policies, generate structured compliance reports, and identify violations with remediation steps.