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 agentmods add skills/kouroshez/coding-os/incident-responsenpx skills add kouroshez/coding-os --skill incident-responsegit clone --depth 1 https://github.com/kouroshez/coding-osWrote 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/kouroshez/coding-os/incident-response)<a href="https://agentmods.dev/skills/kouroshez/coding-os/incident-response"><img src="https://agentmods.dev/badge/skills/kouroshez/coding-os/incident-response.svg" alt="Measured on agentmods" 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.00096 | $0.02830 |
| Opus 5 | $0.00048 | $0.01415 |
| Sonnet 5 | $0.00019 | $0.00566 |
| Haiku 4.5 | $0.00010 | $0.00283 |
Grade A, and why
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 5d 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 — 226 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Incident Response — Stop the Bleeding, Then Diagnose
A practical playbook for handling production incidents and learning from them. Aligned with Google SRE practices and the PagerDuty incident-response framework, refined for 2026 SaaS reality.
When to Use This Skill
- In an incident — pages firing, users complaining, error rate spiked. Load this skill first, before diagnosing.
- Before launch — writing the runbook for a feature.
- After an incident — driving the postmortem.
- Designing the SEV classification.
- Defining the on-call rotation.
- Choosing tools (PagerDuty / Opsgenie / FireHydrant / incident.io).
If the user says "the API is down" / "users can't log in" / "we have an outage" — this skill, immediately.
The Three-Phase Loop
1. Stabilize 2. Diagnose 3. Resolve
(5 min) (30-90 min) (variable)
stop the bleeding understand cause actual fix
│ │ │
└──────────────────┴──────────────────┘
↓
Postmortem (within 5 business days)
The order is fixed. Diagnosis before stabilization wastes the most time, because users keep suffering while you read logs. Stabilize first — even if the fix is hacky — then diagnose.
Phase 1 — Stabilize (the first 5 minutes)
When the page fires:
- Acknowledge the page. Don't drop it on someone else's screen.
- Open the war room. Slack thread, dedicated channel, Zoom — one place for the team.
- Declare a SEV. Stops debate over urgency. See SEV scale below.
- Roll back, scale up, or feature-flag off. In that order of preference.
- Rollback the deploy if the timing matches.
- Scale up if saturation is the signal.
- Flip the feature flag off if a specific feature is broken.
- Communicate. Status page, internal status, customer support team. "We're investigating an issue affecting X." Don't speculate on cause yet.
Hard rule: in the first 5 minutes you take safe reversible actions only. Rollback is reversible. kubectl delete pod is not.
What ships with it
3 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.
- 5d ago First seen · 226 lines · 96 tokens per session scan A 6305d40cc2a7
incident-response is a skill published in the GitHub repository kouroshez/coding-os (6 stars, last pushed 5d ago), licensed Apache-2.0. It adds 96 tokens to every session and 2,830 once invoked, about $0.0005 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-31.
Other skills, from other repositories
graph-mutation-plan
Cookbook for composing an applygraphmutations plan — stable entitykey patterns, the canonical label/edge vocabulary, evidence/invalidation/confidence discipline, and a worked example. Load this when building a non-trivial mutation plan.
potpie-infra-architecture
Use for project infra and architecture context: environments, adapters, runtime configuration, deployments, service dependencies, datastores, API contracts, ownership, incidents, and dependency blast radius.
alfworld-receptacle-finder
Searches for a suitable empty or appropriately occupied receptacle (like a shelf or table) to place an object. Use when you are holding an object that needs to be stored or placed and must find a receptacle that meets the placement criteria. Examines candidate receptacles by navigating to and inspecting each one until…
alfworld-search-pattern-executor
Systematically searches a sequence of likely locations for a target object based on common sense. Use when you need to find a specific object and know which receptacles to check but not which one contains it. Takes a list of candidate receptacles, orchestrates navigation and inspection, and outputs when the target is…
scienceworld-growth-focuser
Use when you have planted a seed or need to track a plant's growth stage (sprouting, flowering, reproduction). Applies the 'focus on' action to a specific plant or biological entity to signal intent and monitor its development. Trigger after planting or when you need to observe life cycle progression in the…
scienceworld-conditional-box-placer
Moves an object to one of two destination containers based on a numeric threshold check. Trigger after a measurement (e.g., temperature) is taken. Place object in 'green' box if value > threshold, or 'blue' box if value < threshold.