sentry-summary

sentry-summary is a skill for Claude Code, Codex from Tracer-Cloud/opensre. It costs 31 tokens per session (426 once invoked), scanned A, original, Apache-2.0.

A workflow for summarising unresolved Sentry errors—reports from an application-monitoring service—by grouping them into themes and ranking them by likely user impact. It can also include uptime information when monitoring is enabled.

In plain words
What is it for?
Use it for Sentry overviews, morning digests, reliability checks, and investigations into the most important application failures.
Why use it?
A long list of error reports does not show which problems matter most. This turns the list into a concise overview of recurring issues, priorities, and service outages or recoveries.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/tracer-cloud/opensre/sentry-summary
Any agent
npx skills add Tracer-Cloud/opensre --skill sentry-summary
Clone the repo
git clone --depth 1 https://github.com/Tracer-Cloud/opensre

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for sentry-summary

README.md
[![agentmods](https://agentmods.dev/badge/skills/tracer-cloud/opensre/sentry-summary.svg)](https://agentmods.dev/skills/tracer-cloud/opensre/sentry-summary)
Your own site
<a href="https://agentmods.dev/skills/tracer-cloud/opensre/sentry-summary"><img src="https://agentmods.dev/badge/skills/tracer-cloud/opensre/sentry-summary.svg" alt="Measured on agentmods" height="20"></a>
Per session 31 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 426 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00031 $0.00426
Opus 5 $0.00015 $0.00213
Sonnet 5 $0.00006 $0.00085
Haiku 4.5 $0.00003 $0.00043

Measured 4d ago against content hash 76d8701926bd, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

sentry-summary 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 4d ago.

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.

integrations/sentry/tools/skills/sentry-summary/SKILL.md · 52 lines

What it actually says

Sentry Summary

Sentry-only (#3 on-demand, #10 morning digest). Multi-source: finish Sentry here, then suggest a multi-source investigation.

1. Fetch issues

search_sentry_issues with query: "is:unresolved":

  • 24h — morning digest, overnight (#10); 7d — "this week", overview.

Max 100 groups per page. Use digest.page_saturated vs page_complete. When completeness is empty, report zero — do not widen unless asked.

2. Fetch uptime

get_sentry_uptime_digest. Skip if uptime_watch_active is false. Include still-down before Issues, recovered after Issues.

3. Classify

digest.structural_clusters → business themes with sample_short_ids.

4. Rank

digest.priority_candidates + business_impact_score, not raw count. Prefer userCount, blockers, regressions; cite impact_reasons.

5. Enrich

Top 3–5 only: get_sentry_issue_details + list_sentry_issue_events (limit 10).

6. Summarise

  • Header + summary bullet counts (Issues + Uptime).
  • [DOWN] above Issues; Issues clusters + priority table; [RECOVERED] after.

Traps

  • count = events/group; issue_count = groups returned
  • page_saturated = first page; completeness: empty = zero groups
  • Uptime needs a running watch schedule — no watch = no data
Changes

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.

  1. 4d ago First seen · 52 lines · 31 tokens per session scan A 76d8701926bd

Subscribe to this mod's changes

sentry-summary is a skill published in the GitHub repository Tracer-Cloud/opensre (10,985 stars, last pushed yesterday), licensed Apache-2.0. It adds 31 tokens to every session and 426 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.