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 github_cligit 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/github_cli)<a href="https://agentmods.dev/skills/tracer-cloud/opensre/github_cli"><img src="https://agentmods.dev/badge/skills/tracer-cloud/opensre/github_cli/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/github_cli"><img src="https://agentmods.dev/badge/skills/tracer-cloud/opensre/github_cli.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 14 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00075 | $0.00592 |
| Opus 5.5 | $0.00030 | $0.00237 |
| Sonnet 5.5 | $0.00015 | $0.00118 |
| Haiku 4.5 | $0.00007 | $0.00059 |
Grade A, and why
operating-github-cli 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-cli
Authenticated gh for OpenSRE. Reads and writes — no approval gate. Prefer over
shell_run / !gh. Pass args after gh; optional repo as owner/name → -R.
Blocked top-level: auth, extension, workflow, run, secret,
codespace, ssh-key, gpg-key, config.
Capabilities
| Intent | Example args |
|---|---|
| Create issue | ["issue", "create", "--title", "…", "--body", "…"] |
| List / view issues | ["issue", "list"] / ["issue", "view", "42"] |
| Close / comment / edit | ["issue", "close", "42"] / ["issue", "comment", "42", "--body", "…"] |
| List / view / close / merge PRs | ["pr", "list"] / ["pr", "view", "45"] / ["pr", "close", "45"] / ["pr", "merge", "45"] |
| Repos / search | ["repo", "list"] / ["search", "issues", "crash"] |
| Arbitrary API | ["api", "repos/OWNER/REPO/issues"] |
After github_cli returns
Use summary when present. Reply short and chat-like.
- Simple (create/close/comment/merge, URL/
#n): plain prose, one sentence. - Structured reads: light chat markdown — short lead-in + bullets
(
* #42 — title); no tables/headers. - Mutate extras: at most 2–4 bullets. No GraphQL/JSON dumps. No "I found:".
- Failure: one sentence from
error/error_type— say it failed to run.
Prefer dedicated tools when they clearly fit
Slack propose/execute; workflow digests; investigation code/commit search. PR CI fix-and-push → fix_github_pr_ci. Security/quality alerts → fix_github_security_alert.
Limitations
gh on PATH; OpenSRE token auth. Action-only — not in gather/investigation.
What ships with it
6 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 tokens per session 8237659d1a20
- 1mo ago Changed · -1 lines fb089970daa7
- 1mo ago First seen · 50 lines · 72 tokens per session scan A 24b0196b5a38
operating-github-cli is a skill published in the GitHub repository Tracer-Cloud/opensre (12,005 stars, last pushed today), licensed Apache-2.0. It adds 75 tokens to every session and 592 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
batch
Research and plan a large-scale change, then execute it in parallel across 5–30 isolated worktree agents that each open a PR.
team-release
Orchestrate the release team — release-manager, qa-lead, devops-engineer, producer — to execute a release from candidate to deployment.
github
Drive GitHub via the official gh CLI — repos, issues, pull requests, releases, gists, Actions runs, and raw REST through gh api. Use when the user asks to inspect or manage GitHub.
testdino-releases
Use when the user wants to browse, inspect, create, or update releases/milestones in a TestDino project. Covers listreleases, getrelease, createrelease, and updaterelease. Accepts counter-style IDs like MS-12.
create-milestone
Create a GitHub milestone for an upcoming release. Suggests the next version based on the latest release, gathers all merged PRs and closed issues since that release, presents a draft with two tables (Issues and PRs) for user approval, then creates the milestone and assigns all approved items.
shiplog
Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.