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 repair-github-cigit 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/repair-github-ci)<a href="https://agentmods.dev/skills/tracer-cloud/opensre/repair-github-ci"><img src="https://agentmods.dev/badge/skills/tracer-cloud/opensre/repair-github-ci/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/repair-github-ci"><img src="https://agentmods.dev/badge/skills/tracer-cloud/opensre/repair-github-ci.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.00040 | $0.01057 |
| Opus 5 | $0.00020 | $0.00528 |
| Sonnet 5 | $0.00008 | $0.00211 |
| Haiku 4.5 | $0.00004 | $0.00106 |
Grade A, and why
repair-github-ci 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 today.
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.
How it starts
The opening of the file, as written. The whole thing — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub CI fix
Use fix_github_pr_ci to repair failing checks on a pull request or a named
branch.
When to use
- The user asks to fix failing CI, broken GitHub Actions checks, failing PR
checks, a red pull request branch, or CI on a named branch such as
main. - The user says "fix CI on this PR", "fix the CI of PR 123 and push", "repair the failing checks on owner/repo#123", or provides a GitHub pull request URL and asks for CI/check fixes.
- The user asks to fix failing CI on a branch itself — "fix the CI on main", "main is red, fix it", or "fix CI on the default branch and push" — with no PR involved.
Related workflows
- Ordinary PR reads, comments, closes, merges, labels, or issue work. Use
github_cli. - Security alert remediation. Use
fix_github_security_alert.
Workflow rules
- For a GitHub PR URL, call:
fix_github_pr_ci(pr_url="<url>") - For
owner/repo#123or "PR 123 in owner/repo", call:fix_github_pr_ci(owner="owner", repo="repo", pr_number=123) - For "fix the CI on main" (or any named branch with no PR), call:
fix_github_pr_ci(branch="main")Never passbranchtogether with a PR selector, and never invent a branch the user did not name. - If no owner/repo is named, omit both and let the tool use the current checkout's GitHub origin.
- Never use
github_cliorshell_runto run rawgh pr checks,gh run view, checkout, commit, or push for this workflow. The CI fixer owns PR metadata, failing-check log inspection, fix execution, branch safety, commit, and push. - The tool pushes to the existing PR head branch after approval. Do not ask the user whether to open a new PR.
- A PR that is behind its base branch, or conflicts with it (GitHub shows it
as not mergeable and starts no checks), is handled by the tool: it merges the
base branch into the PR branch, resolves conflicts, regenerates lockfiles,
pushes, and waits for the checks — also when the conflict only appears after
its own push. Never run
git merge,git rebase, or conflict edits around it. If it reports blocked files, relay that one line and stop. - For branch targets such as
main, the tool creates a separate linked git worktree, commits on a freshopensre/ci-fix-*branch, and pushes that branch. It never pushes directly to protected branches. - If the tool returns
response_text, output exactly that text and stop. - If
error_kindis set, reply in one short line fromerror. Do not say "next steps", do not add numbered options, do not list example commands, and do not ask a broad follow-up question.
What ships with it
1 file 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.
- today First seen · 105 lines · 40 tokens per session scan A 806f4c09a2d3
repair-github-ci is a skill published in the GitHub repository Tracer-Cloud/opensre (11,064 stars, last pushed today), licensed Apache-2.0. It adds 40 tokens to every session and 1,057 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-15.
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.