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 vasilyu1983/AI-Agents-public --skill ops-incident-responsegit clone --depth 1 https://github.com/vasilyu1983/AI-Agents-publicWrote 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/vasilyu1983/ai-agents-public/ops-incident-response)<a href="https://agentmods.dev/skills/vasilyu1983/ai-agents-public/ops-incident-response"><img src="https://agentmods.dev/badge/skills/vasilyu1983/ai-agents-public/ops-incident-response/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/vasilyu1983/ai-agents-public/ops-incident-response"><img src="https://agentmods.dev/badge/skills/vasilyu1983/ai-agents-public/ops-incident-response.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.00042 | $0.03982 |
| Opus 5 | $0.00021 | $0.01991 |
| Sonnet 5 | $0.00008 | $0.00796 |
| Haiku 4.5 | $0.00004 | $0.00398 |
Grade A, and why
ops-incident-response 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 9d 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.
How it starts
The opening of the file, as written. The whole thing — 240 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Incident Response
Production incident management: detect, triage, mitigate, resolve, learn. This skill covers the human and process side of incidents, not the infrastructure automation (use ops-devops-platform for that).
Quick Reference
| Need | Go to |
|---|---|
| Classify the incident severity | ## Severity Classification |
| Run the end-to-end response loop | ## Workflow |
| Coordinate as incident commander | ## Incident Commander Checklist |
| Send status or stakeholder updates | ## Communication Templates |
| Use templates and runbooks | ## Navigation |
Scope
| Use For | Do NOT Use For |
|---|---|
| Severity classification and escalation | Infrastructure provisioning or CI/CD |
| On-call runbook design and review | Application resilience patterns (retries, circuit breakers) |
| Incident commander workflows | Monitoring/alerting tool setup |
| Status page and stakeholder communication | Root cause analysis of code bugs |
| Blameless postmortem facilitation | Performance benchmarking |
| MTTD/MTTR measurement and improvement | Security incident forensics (use software-security-appsec) |
Severity Classification
| Level | Criteria | Response time | Who is paged |
|---|---|---|---|
| SEV1 | Revenue-impacting, data loss, full outage | Immediate | On-call + incident commander + leadership |
| SEV2 | Degraded service, partial outage, SLO breach | 15 min | On-call + incident commander |
| SEV3 | Minor degradation, workaround available | 1 hour | On-call |
| SEV4 | Cosmetic, no user impact, internal tooling | Next business day | Ticket owner |
ASCII Flow
Alert, user report, or suspected incident
-> Detect and acknowledge within SLA
-> Open incident channel and assign roles
-> Triage impact, blast radius, and severity
-> Communicate status and next update time
-> Mitigate user impact before deep root-cause work
-> Verify recovery with metrics and smoke tests
-> Resolve, close comms, and schedule postmortem
-> Feed action items back into runbooks, alerts, and platform work
What ships with it
14 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.
- agents/openai.yaml 360 B
- assets/incident-channel-template.md 198 B
- assets/postmortem-template.md 1.0 KB
- assets/runbook-template.md 201 B
- data/sources.json 7.0 KB
- learnings.consolidated.md 597 B
- learnings.md 614 B
- references/control-theory-applied.md 34 KB
- references/decision-theory-applied.md 38 KB
- references/incident-metrics-guide.md 2.0 KB
- references/on-call-practices.md 811 B
- references/postmortem-facilitation.md 1.6 KB
- references/runbook-design-guide.md 879 B
- references/slo-incident-triggering.md 3.5 KB
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.
- 9d ago First seen · 240 lines · 42 tokens per session scan A 67a826d73f8c
ops-incident-response is a skill published in the GitHub repository vasilyu1983/AI-Agents-public (87 stars, last pushed 10d ago), licensed MIT. It adds 42 tokens to every session and 3,982 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-03.
Other skills, from other repositories
parallel-feature-development
Coordinate parallel feature development with file ownership strategies, conflict avoidance rules, and integration patterns for multi-agent implementation. Use this skill when decomposing a large feature into independent work streams, when two or more agents need to implement different layers of the same system…
saga-orchestration
Implement saga patterns for distributed transactions and cross-aggregate workflows. Use this skill when implementing distributed transactions across microservices where 2PC is unavailable, designing compensating actions for failed order workflows that span inventory, payment, and shipping services, building…
task-coordination-strategies
Decompose complex tasks, design dependency graphs, and coordinate multi-agent work with proper task descriptions and workload balancing. Use this skill when breaking down work for agent teams, managing task dependencies, or monitoring team progress.
bazel-build-optimization
Optimize Bazel builds for large-scale monorepos. Use when configuring Bazel, implementing remote execution, or optimizing build performance for enterprise codebases.
nx-workspace-patterns
Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.
context-driven-development
Creates and maintains project context artifacts (product.md, tech-stack.md, workflow.md, tracks.md) in a conductor/ directory. Scaffolds new projects from scratch, extracts context from existing codebases, validates artifact consistency before implementation, and synchronizes documents as the project evolves. Use when…