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/expensify/app/sentrynpx skills add Expensify/App --skill sentrygit clone --depth 1 https://github.com/Expensify/AppWhat 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.00037 | $0.00452 |
| Opus 5 | $0.00018 | $0.00226 |
| Sonnet 5 | $0.00007 | $0.00090 |
| Haiku 4.5 | $0.00004 | $0.00045 |
Grade A, and why
sentry 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.
What it actually says
Sentry
When to Use This Skill
Use Sentry skill when:
- User requests any data from Sentry
- User asks about performance metrics or span summary
- User want to compare metrics between any date ranges
- User asks about latest production crashes and issues
- User want to investigate profiles or traces from production sessions
Sentry MCP
The Sentry MCP server is configured in .mcp.json and gives Claude Code direct access to Sentry.
Prerequisites
Setup (one-time per engineer): On first use, Claude Code will open a browser OAuth login to Sentry. Sign in and authorize — no manual token setup required.
Available MCP Tools
Use these tools for data analysis:
| Tool | Purpose |
|---|---|
mcp__sentry__find_releases |
Find release versions for scoping queries |
mcp__sentry__search_issues |
Search for errors/crashes by query, project, date range |
mcp__sentry__search_events |
Query raw events/spans (performance data, durations) |
mcp__sentry__search_issue_events |
Get individual events for a known issue ID |
mcp__sentry__get_issue_tag_values |
Inspect tag distributions (e.g. device, version) on an issue |
mcp__sentry__get_sentry_resource |
Fetch a specific Sentry resource by URL/ID |
Do not use mcp__sentry__analyze_issue_with_seer — AI analysis is out of scope for this skill.
Always use:
- org slug:
expensify - project slug:
app
Example uses
- "Search Sentry for crashes in the last 24h related to expense creation"
- "Get details on Sentry issue APP-123"
- "Compare P90 of ManualAppStartup durations between last two weeks"
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 · 48 lines · 37 tokens per session scan A 777aadbecd4e
sentry is a skill published in the GitHub repository Expensify/App (5,015 stars, last pushed yesterday), licensed MIT. It adds 37 tokens to every session and 452 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-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…