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/drafthq/draft/incident-responsenpx skills add drafthq/draft --skill incident-responsegit clone --depth 1 https://github.com/drafthq/draftWhat 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 | $0.00041 | $0.02126 |
| Opus 5 | $0.00020 | $0.01063 |
| Sonnet 5 | $0.00008 | $0.00425 |
| Haiku 4.5 | $0.00004 | $0.00213 |
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 2d 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.
- Use `curl`/`wget` to fetch dashboards or error pages mentioned How it starts
The opening of the file, as written. The whole thing — 249 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Incident Response
You are managing an incident through its full lifecycle using structured incident management practices.
Red Flags — STOP if you're
- Fixing before communicating (stakeholders must know first)
- Skipping severity classification
- Writing a postmortem with blame (blameless only)
- Closing an incident without prevention items
- Ignoring rollback as a mitigation option
Communicate first. Fix second. Learn always.
Pre-Check
- Check for Draft context:
ls draft/ 2>/dev/null
This skill works standalone — incidents don't wait for project setup.
- If available, follow the base procedure in
core/shared/draft-context-loading.md.
Step 1: Parse Arguments
/draft:incident-response new <description>— Start new incident/draft:incident-response update <status>— Post status update/draft:incident-response postmortem— Generate postmortem report/draft:incident-response(no args) — Interactive: ask which mode
NEW Mode — Start Incident
Step 2: Triage
Classify severity:
| Level | Response Time | Who | Examples |
|---|---|---|---|
| SEV1 | Immediate, all-hands | Entire team | Data loss, complete outage, security breach |
| SEV2 | 15 minutes | On-call + team lead | Major feature broken, significant degradation |
| SEV3 | 1 hour | On-call | Minor feature broken, workaround exists |
| SEV4 | Next business day | Assigned engineer | Cosmetic issue, minor inconvenience |
Assess:
- What is broken? (from description or Jira ticket)
- Who is affected? (from
draft/product.mduser types if available) - What is the blast radius? (from
draft/.ai-context.mdservice topology if available) - Is data at risk? (escalate to SEV1 if yes)
Step 3: Communicate
Generate initial status update:
INCIDENT: {description}
Severity: SEV{1-4}
Impact: {who/what is affected}
Status: Investigating
Commander: {name or "unassigned"}
Next update: {time — SEV1: 15min, SEV2: 30min, SEV3: 1hr}
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.
- 2d ago First seen · 249 lines · 41 tokens per session scan A db3afdeda7a0
incident-response is a skill published in the GitHub repository drafthq/draft (40 stars, last pushed 14d ago), licensed MIT. It adds 41 tokens to every session and 2,126 once invoked, about $0.0002 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
memorix-memory
Use when prior workspace context, past decisions, solved bugs, handoff state, or durable project knowledge would help a coding task.
memorix
Use when Claude Code needs Memorix shared memory, reasoning, Git Memory, mini-skills, session handoff, orchestration coordination, or integration troubleshooting.
memorix-mini-skills
Use when durable project knowledge, gotchas, workflows, or repeated fixes should become reusable agent guidance instead of ordinary memory.
memorix-orchestrate
Use when a main agent needs Memorix to coordinate explicit subagent work through tasks, handoffs, messages, file locks, or the orchestrate CLI.
memorix-reasoning
Use when a technical decision, trade-off, rejected alternative, architecture rationale, or design risk should be recorded or recovered.
memorix-sessions
Use when resuming work, preparing handoff context, binding an HTTP control-plane project, or deciding whether sessionstart is useful.