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 sev1-first-15-minutesgit 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/sev1-first-15-minutes)<a href="https://agentmods.dev/skills/bregman-arie/devops-sre-skills/sev1-first-15-minutes"><img src="https://agentmods.dev/badge/skills/bregman-arie/devops-sre-skills/sev1-first-15-minutes/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/sev1-first-15-minutes"><img src="https://agentmods.dev/badge/skills/bregman-arie/devops-sre-skills/sev1-first-15-minutes.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.00021 | $0.00407 |
| Opus 5 | $0.00010 | $0.00204 |
| Sonnet 5 | $0.00004 | $0.00081 |
| Haiku 4.5 | $0.00002 | $0.00041 |
Grade A, and why
Sev1 First 15 Minutes 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 for a confirmed high-severity production incident.
Preconditions
- You have an incident channel and a path to page additional responders.
Procedure
- Declare severity and open an incident channel.
- Assign roles: incident commander, comms lead, operations lead.
- State the customer impact in one sentence.
- Stabilize first: stop the bleeding (rollback, disable feature, shed load).
- Start a timeline and capture key actions/decisions.
Decision points
- If impact is unknown: prioritize measurement and narrowing scope.
- If rollback is low-risk and likely effective: rollback early.
- If data integrity is at risk: freeze writes and escalate.
Verification
- Leading indicators improve (error rate, latency, saturation).
- Customer reports decrease.
- Comms cadence is established.
Rollback / undo
- If mitigation worsens impact, revert and try the next lowest-risk action.
Escalation
- Escalate to security if incident involves auth, data exposure, or suspicious activity.
- Escalate to leadership if SLA/SLO breach is likely.
Examples
Initial update template:
Impact: <who/what is affected>
Start: <time>
Current status: <what we see>
Mitigation in progress: <what we are doing>
Next update: <time>
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 · 72 lines · 21 tokens per session scan A 4e71990dd189
Sev1 First 15 Minutes 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 21 tokens to every session and 407 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
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.
incident-response
Stabilize, diagnose, fix, and learn from a production incident. Invoke when something is on fire, when paged, or when users report a regression.
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.
incident-response-skill
A skill that uses object-style tool references with purpose descriptions and required flags, plus strict validation.
incident-response
Use to run an incident response workflow — initial triage, status updates during, blameless postmortem after. Do NOT use for ordinary debugging — use debugging-strategies for single-engineer bug-hunting.
cloudflare-observability-mcp
Observability MCP server by Cloudflare.