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-reportgit 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-report)<a href="https://agentmods.dev/skills/tahirraufkeeyu/software-development-agent-stack--sdas/incident-report"><img src="https://agentmods.dev/badge/skills/tahirraufkeeyu/software-development-agent-stack--sdas/incident-report/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-report"><img src="https://agentmods.dev/badge/skills/tahirraufkeeyu/software-development-agent-stack--sdas/incident-report.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.00063 | $0.02365 |
| Opus 5 | $0.00032 | $0.01182 |
| Sonnet 5 | $0.00013 | $0.00473 |
| Haiku 4.5 | $0.00006 | $0.00236 |
Grade A, and why
incident-report 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 10d 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 — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When to use
Trigger this skill when:
- An incident (any severity) has been declared resolved and the team needs a written postmortem.
- A customer or leadership stakeholder has asked for a writeup of what happened.
- A recurring issue needs a formal record to spot patterns across incidents.
Do not use this skill for:
- Mid-incident communication (use
engineering:incident-response). - Security vulnerability disclosure to external parties (follow the formal security process).
- Routine bug triage notes (use a ticket, not a postmortem).
Inputs
Required:
- Incident ID (e.g.,
INC-2026-03-14-01) or the Slack channel name (e.g.,#incident-api-5xx-2026-03-14). - Start and end timestamps of the incident (UTC preferred).
- At minimum one source of truth: Slack channel transcript, PagerDuty incident link, or log excerpts.
Optional:
- Links to dashboards, commit SHAs of the change that introduced the issue, and the revert PR.
- Names and roles of the responders (IC, comms lead, scribe).
- Prior related incidents.
Outputs
A single Markdown postmortem following the structure in references/incident-template.md:
- Header with incident ID, severity, status, duration, impact summary
- One-paragraph summary (2–3 sentences)
- Timeline in UTC (who did what, when)
- Detection (how did we find out, how long until detection)
- Response (what we did, what worked, what did not)
- Root cause analysis with 5 whys
- Contributing factors
- What went well / what did not
- Action items table: Item | Owner | Due | Ticket | Priority
- Lessons learned
- Related incidents
Tool dependencies
- Slack MCP —
slack_read_channel,slack_search_publicto pull the incident channel transcript in order. - PagerDuty MCP (if available) — for incident start/end timestamps, severity, and responder list.
- GitHub MCP — to find the offending PR (via
git bisector by searching for the revert commit) and the resolving PR. - Bash —
git log --before --afterto scope commits around the incident. - Grep / Read — to pull log excerpts from local files if logs were exported.
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.
- 10d ago First seen · 164 lines · 63 tokens per session scan A da186f12efee
incident-report is a skill published in the GitHub repository tahirraufkeeyu/software-development-agent-stack--sdas (18 stars, last pushed 4mo ago), licensed MIT. It adds 63 tokens to every session and 2,365 once invoked, about $0.0003 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…