OpenSRE is an open-source framework for building AI agents that investigate and resolve production incidents using operational data and tools. It is for site reliability engineers who want customizable incident-response workflows, training, and evaluation on their own infrastructure.
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 skills add Tracer-Cloud/opensre --skill summarizing-sentry-issuesgit clone --depth 1 https://github.com/Tracer-Cloud/opensreWrote 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/tracer-cloud/opensre/summarizing-sentry-issues)<a href="https://agentmods.dev/skills/tracer-cloud/opensre/summarizing-sentry-issues"><img src="https://agentmods.dev/badge/skills/tracer-cloud/opensre/summarizing-sentry-issues/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/tracer-cloud/opensre/summarizing-sentry-issues"><img src="https://agentmods.dev/badge/skills/tracer-cloud/opensre/summarizing-sentry-issues.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00035 | $0.00429 |
| Opus 5 | $0.00017 | $0.00215 |
| Sonnet 5 | $0.00007 | $0.00086 |
| Haiku 4.5 | $0.00003 | $0.00043 |
Grade A, and why
summarizing-sentry-issues 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 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 returnedpage_saturated= first page;completeness: empty= zero groups- Uptime needs a running watch schedule — no watch = no data
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 · 52 lines · 35 tokens per session scan A 1cc106af7365
summarizing-sentry-issues is a skill published in the GitHub repository Tracer-Cloud/opensre (11,026 stars, last pushed yesterday), licensed Apache-2.0. It adds 35 tokens to every session and 429 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-10.
Other skills, from other repositories
host_bash
A read-only shell skill for examining files and running diagnostic commands in a restricted environment. A shell is a text interface for operating-system commands.
datadog
Full-stack observability with Datadog APM, logs, metrics, synthetics, and RUM. Use when implementing monitoring, tracing, alerting, or cost optimization for production systems.
host_files
A set of tools for investigating a device’s file system, including finding large files, checking directory disk usage, and inspecting individual files.
dd-debugger
Live Debugger - inspect runtime argument/variable values in production by placing log probes on methods. Use when asked what values a function receives, what parameters look like at runtime, or to capture live data from running services without redeploying.
dd-triage-flaky-test
Load when investigating a specific flaky test. Gets history, failure pattern, and category, then recommends fix, quarantine, or escalate.
dd-unblock-pr
Load when investigating a failing PR CI pipeline or checking PR health. Attributes each CI failure as flaky, infra, or regression, proposes a targeted action, and reports code coverage.