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 bregman-arie/devops-sre-skills --skill triage-error-budget-burngit clone --depth 1 https://github.com/bregman-arie/devops-sre-skillsWrote 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/bregman-arie/devops-sre-skills/triage-error-budget-burn)<a href="https://agentmods.dev/skills/bregman-arie/devops-sre-skills/triage-error-budget-burn"><img src="https://agentmods.dev/badge/skills/bregman-arie/devops-sre-skills/triage-error-budget-burn/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/bregman-arie/devops-sre-skills/triage-error-budget-burn"><img src="https://agentmods.dev/badge/skills/bregman-arie/devops-sre-skills/triage-error-budget-burn.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.00025 | $0.00399 |
| Opus 5 | $0.00013 | $0.00199 |
| Sonnet 5 | $0.00005 | $0.00080 |
| Haiku 4.5 | $0.00003 | $0.00040 |
Grade A, and why
Triage Error Budget Burn 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 12d 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
When to use
Use when burn alerts fire or SLO dashboards show accelerated error budget consumption.
Preconditions
- The SLO definition and signals are known (good/bad events or latency threshold).
Procedure
- Confirm the SLO signal and the burn window.
- Identify whether burn is driven by errors, latency, or missing telemetry.
- Break down by endpoint, region, customer segment, and dependency.
- Correlate with deploys, config changes, and incidents.
- Choose the fastest mitigation that reduces burn (rollback, disable, scale, failover).
Decision points
- Telemetry missing: fix instrumentation/pipeline to avoid false burn.
- Dependency-induced burn: mitigate upstream (timeouts, circuit breaker, failover).
- Deploy-correlated burn: rollback or feature flag off.
Verification
- Burn rate returns to normal and stays stable.
- Alert conditions clear.
Rollback / undo
- Revert mitigations that cause new errors or correctness regressions.
Escalation
- Escalate to dependency owners if they are the dominant contributor.
- Escalate to service owners for code fixes.
Examples
Start by decomposing the SLO into error vs latency vs availability contributions.
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.
- 12d ago First seen · 66 lines · 25 tokens per session scan A ad528fdb0ee0
Triage Error Budget Burn is a skill published in the GitHub repository bregman-arie/devops-sre-skills (22 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 25 tokens to every session and 399 once invoked, about $0.0001 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-08-30.
Other skills, from other repositories
k8s-incident-triage
Read-only Kubernetes incident triage using kubectl. Accepts natural language or structured input. Produces root-cause hypotheses, evidence, and next-step commands.
sre-expert
Expert-level site reliability engineering, SLOs, incident management, and operational excellence. Use when the user mentions reliability, monitoring, incident management, SLOs, or observability, or when the task involves SRE Fundamentals, Reliability Practices, SRE Principles, or On-Call.
sre_triage
SRE first-response triage for distributed training incidents. Automates the manual checks from PyTorch/NCCL debugging runbooks.
slo-architect
Use when defining, reviewing, or operating SLOs/SLIs/error budgets. Triggers on "define an SLO", "what should our SLO be", "error budget", "burn rate", "SLI", "service level objective", "Google SRE workbook", "multi-window burn-rate alert", or any reliability-target question. Ships SLO designer, error-budget…
reliability-engineering
SRE principles, observability, and incident management.
pager-triage
AI-powered incident triage for PagerDuty. List active incidents, deep-dive with timeline and alert correlation, check on-call schedules, acknowledge, resolve, and annotate — all from your agent. Read-only by default; write operations require explicit --confirm.