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 delivering-morning-briefingsgit 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/delivering-morning-briefings)<a href="https://agentmods.dev/skills/tracer-cloud/opensre/delivering-morning-briefings"><img src="https://agentmods.dev/badge/skills/tracer-cloud/opensre/delivering-morning-briefings/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/delivering-morning-briefings"><img src="https://agentmods.dev/badge/skills/tracer-cloud/opensre/delivering-morning-briefings.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.00036 | $0.01927 |
| Opus 5.5 | $0.00014 | $0.00771 |
| Sonnet 5.5 | $0.00007 | $0.00385 |
| Haiku 4.5 | $0.00004 | $0.00193 |
Grade A, and why
delivering-morning-briefings scanned grade A with 1 finding 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 1mo 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
blocks, or a `curl` dump. The news fetch below extracts plain-text headlines. How it starts
The opening of the file, as written. The whole thing — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Morning report
Fetch live weather and news, compose a plain-text briefing, deliver it, and offer a recurring schedule.
When to use
Use for requests such as "morning report", "morning briefing", "daily brief", "give me my morning update", or "weather and news summary".
Workflow rules
Fetch the raw inputs first with read-only shell commands, one shell_run
per response, and wait for both results before composing or delivering.
Complete this workflow in the current agent; do not start an investigation
that produces a second, unrelated status report.
Never fabricate weather values or headlines. Treat RSS/XML/HTML as intermediate
data. Show only the composed briefing, without raw feed markup, XML tags, CDATA
blocks, or a curl dump. The news fetch below extracts plain-text headlines.
Plan
The fetches run quietly, so track progress with the update_plan tool, not
with headers or prose:
- On entry, before the fetches, call
update_planwith these steps verbatim, the first stepin_progress, and a one-lineexplanation(this is not a diagnosis; no hypothesis table):Fetch weather and headlines/Compose the briefing/Deliver the briefing/Offer a recurring schedule. Steps 1–2 below are two consecutive responses that share the first plan step. - After a step's tool results, call
update_planmarking itcompletedand the next stepin_progress, in the same response as the next step's single tool call. - Do not narrate the plan or repeat step names in prose; the shell renders the checklist. The composed briefing itself (step 3) and the schedule offer's response_text (step 5) stay exactly as specified below — the plan tracks around them, never replaces them.
Workflow
1. Fetch weather
Fetch today's weather with shell_run. Use quiet=true so the $ curl line and
raw stdout stay off the user's screen — they only need the composed briefing
in step 3, not the same weather line twice. Use the city the user named; if
none is given, use their configured/default city, else omit the location:
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.
- 1mo ago Changed a225b418c34d
- 1mo ago Changed · -2 lines 4f1ac038090d
- 1mo ago First seen · 170 lines · 36 tokens per session scan A b0c4485d3575
delivering-morning-briefings is a skill published in the GitHub repository Tracer-Cloud/opensre (12,549 stars, last pushed today), licensed Apache-2.0. It adds 36 tokens to every session and 1,927 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-10.
Other skills, from other repositories
monitoring-alerting-commerce
Track store health in real time with dashboards for checkout success rate, payment failures, cart errors, and custom SLO alerting.
grafana-expert
Expert-level Grafana dashboards, visualization, data sources, alerting, and production operations. Use when the user mentions dashboards, visualization, monitoring, observability, or alerting, or when the task involves Grafana Architecture, Installation on Kubernetes, Data Sources, or Dashboard JSON.
monitoring-expert
Expert-level monitoring and observability with Prometheus, Grafana, logging, and alerting. Use when the user mentions observability, Prometheus, Grafana, logging, metrics, or alerting, or when the task involves The Three Pillars of Observability, Monitoring Fundamentals, Prometheus Configuration, or Alert Rules.
grafana
Build operable Grafana dashboards with template variables, provisioning-as-code, and unified alerts wired to Prometheus/Loki; avoid high-cardinality panels agents love to ship.
datadog
Full-stack observability with Datadog APM, logs, metrics, synthetics, and RUM. Use when implementing monitoring, tracing, alerting, or cost optimization for production systems.
monitoring-logging
Application monitoring, logging systems, and alerting.