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 security_fixgit 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/security_fix)<a href="https://agentmods.dev/skills/tracer-cloud/opensre/security_fix"><img src="https://agentmods.dev/badge/skills/tracer-cloud/opensre/security_fix/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/security_fix"><img src="https://agentmods.dev/badge/skills/tracer-cloud/opensre/security_fix.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00066 | $0.00524 |
| Opus 5.5 | $0.00026 | $0.00210 |
| Sonnet 5.5 | $0.00013 | $0.00105 |
| Haiku 4.5 | $0.00007 | $0.00052 |
Grade A, and why
operating-github-security-fixer 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 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.
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
operating-github-security-fixer
Use fix_github_security_alert for GitHub security remediation requests, not
github_cli or shell_run.
Rules:
- Dependabot, code-scanning/CodeQL alerts, and Code Quality standard findings are supported.
- Secret-scanning alerts are refused by the tool; tell the user to rotate or revoke the secret first.
- For a broad repo request, omit
alert_numberand usealert_type="auto"so the tool selects one open supported security or quality finding by severity. - If the user says "hey fix the security issues" without a repo, omit
ownerandrepo; the tool uses the current checkout's GitHub origin. - For GitHub
/security/code-scanningpages or CodeQL/code-scanning backlog requests, passalert_type="code_scanning". - For GitHub
/security/qualitypages or quality backlog requests, passalert_type="code_quality". - The tool fixes findings itself: built-in fixers first, then an auto-detected
coding agent CLI. Never add coding-agent advice, CLI names, or install
commands beyond what the tool's
errortext already says. - If the tool returns
response_text, output exactly that text and stop. - If no automatic patch is produced, keep the reply to one short line from
error; do not say "next steps", add numbered options, list example commands, or ask a broad follow-up question. - Set
open_pr=trueonly when the user asks to open, raise, create, or ship a pull request. - With
open_pr=trueand a named repository, omitworkspacefor an isolated checkout. Local-only fixes use the configured workspace; an explicit checkout must match the target repository. - The tool runs one alert per call. Do not loop over multiple alerts unless the user explicitly asks to continue after the first result.
- Report the result from
summary,changed_files,branch_name, andpr_url.
What ships with it
9 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.
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 · +3 lines 5e7fd784c4a3
- 1mo ago Changed · +3 tokens per session 756a2a6e63b4
- 1mo ago First seen · 39 lines · 63 tokens per session scan A 22c1346280e4
operating-github-security-fixer is a skill published in the GitHub repository Tracer-Cloud/opensre (12,513 stars, last pushed today), licensed Apache-2.0. It adds 66 tokens to every session and 524 once invoked, about $0.0003 per session on Opus 5.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
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.