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 tahirraufkeeyu/software-development-agent-stack--sdas --skill incident-responsegit clone --depth 1 https://github.com/tahirraufkeeyu/software-development-agent-stack--sdasWrote 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/tahirraufkeeyu/software-development-agent-stack--sdas/incident-response)<a href="https://agentmods.dev/skills/tahirraufkeeyu/software-development-agent-stack--sdas/incident-response"><img src="https://agentmods.dev/badge/skills/tahirraufkeeyu/software-development-agent-stack--sdas/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/tahirraufkeeyu/software-development-agent-stack--sdas/incident-response"><img src="https://agentmods.dev/badge/skills/tahirraufkeeyu/software-development-agent-stack--sdas/incident-response.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.00059 | $0.02260 |
| Opus 5 | $0.00030 | $0.01130 |
| Sonnet 5 | $0.00012 | $0.00452 |
| Haiku 4.5 | $0.00006 | $0.00226 |
Grade A, and why
incident-response scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- `promtool`/`curl` to hit Prometheus. How it starts
The opening of the file, as written. The whole thing — 210 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When to use
- A pager just went off and severity is unclear.
- Production is degraded and the on-call needs a structured loop.
- A deploy triggered an SLO breach and you need to decide roll-back vs. roll-forward.
- After mitigation, to draft the postmortem while memory is fresh.
Do not use for general debugging of a feature bug in dev — use the engineering:debug skill. Do not use for known-good maintenance work.
Inputs
alert— alert title, dashboard link, and first-firing timestamp (UTC).service— service name impacted (orunknownif still triaging).environment—prod|staging| multi-region (us-east-1,eu-west-1).symptoms— observed customer impact: errors, latency, outage, partial.recent_changes— last 3 deploys and last 3 infra changes (get from CI history).log_sources— which ofkubectl, CloudWatch, Loki, Datadog, Splunk are available.severity_guess— initial guess (SEV1 total outage, SEV2 major degradation, SEV3 minor).
Outputs
- Triage notes captured in the incident channel (timestamped lines).
- Confirmed severity and blast radius.
- Mitigation action taken with evidence that it worked.
- Slack status updates (initial, update every 30 min during active, resolution).
- Draft postmortem using
references/postmortem-template.mdwithin 24 hours of resolution.
Tool dependencies
kubectlwith context set to the affected cluster.helmfor rollback.- AWS CLI /
az/gcloudfor cloud-side evidence. logcli(Loki) or cloud log CLIs (aws logs tail,az monitor).promtool/curlto hit Prometheus.ghCLI to pull recent deploys.- Slack MCP or webhook for status posts.
Procedure
0. Declare
Open (or acknowledge) an incident in PagerDuty/Opsgenie. Create a dedicated Slack channel: #inc-<yyyymmdd>-<short-desc>. Assign roles:
- Incident Commander (IC) — decisions, communication.
- Ops lead — runs the procedure below.
- Scribe — timestamped notes into the channel (UTC).
- Comms — external status page + customer comms.
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.
- 9d ago First seen · 210 lines · 59 tokens per session scan A 6d1928a7606e
incident-response is a skill published in the GitHub repository tahirraufkeeyu/software-development-agent-stack--sdas (18 stars, last pushed 4mo ago), licensed MIT. It adds 59 tokens to every session and 2,260 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.