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 davekilleen/Dex --skill incident-reviewgit clone --depth 1 https://github.com/davekilleen/DexWrote 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/davekilleen/dex/incident-review)<a href="https://agentmods.dev/skills/davekilleen/dex/incident-review"><img src="https://agentmods.dev/badge/skills/davekilleen/dex/incident-review/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/davekilleen/dex/incident-review"><img src="https://agentmods.dev/badge/skills/davekilleen/dex/incident-review.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.00032 | $0.01144 |
| Opus 5.5 | $0.00013 | $0.00458 |
| Sonnet 5.5 | $0.00006 | $0.00229 |
| Haiku 4.5 | $0.00003 | $0.00114 |
Grade A, and why
incident-review 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 1mo 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Incident review
When to use
Use this skill after or during a contained incident when people need a trustworthy timeline, impact record, contributing-conditions analysis, and prevention follow-up.
Do not use it as a substitute for live containment, paging, emergency escalation, or security/legal reporting. Not for attributing personal blame, filling gaps with a plausible root cause, or reviewing an event without cited evidence.
Inputs and source discipline
Collect an incident identifier, review scope, start and end bounds, affected systems, and the review as-of date/time. Use a named IANA timezone when available and preserve each source's original timestamp and timezone or offset.
Create an evidence ledger for logs, alerts, deploy records, traces, tickets, support reports, communications, and interviews. For every event or impact claim record the source, source date, as-of date/time, locator, timestamp precision, and freshness. Record missing sources and access limits as unknown rather than compensating with memory. Keep raw evidence separate from analysis.
Method
- Define the incident boundary and affected service or users from cited evidence. Do not invent severity, duration, counts, percentages, or business impact.
- Build a timezone-aware timeline. Preserve the reported timestamp and timezone, add a normalized timestamp only when conversion is valid, and cite the source for every row. If two credible sources disagree, retain both rows and mark the point contradictory instead of forcing an order.
- Separate facts (directly observed or cited), hypotheses (inferred explanations), unknowns, stale evidence, and contradictions. Test a hypothesis against available evidence; do not call it a cause or root cause until the evidence supports that wording.
- Use a blameless method: describe system conditions, incentives, interfaces, safeguards, detection, response, and recovery. Name actions and controls, not people as the cause. Explain what was reasonable to know at the time.
- Define prevention and detection actions with the failure mode they address, a
proof or acceptance measure, a follow-up date only when evidenced, and an owner.
Use
TBDfor an unassigned owner or date; never guess an owner or make a status claim from an unchecked task list. - Present recommendations and follow-up choices to the human authority. A recommendation is not a human decision, and prevention work is not complete until its proof is read back.
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.
- 1mo ago Changed · +2 lines 050792872583
- 1mo ago First seen · 104 lines · 32 tokens per session scan A c2d0500ba356
incident-review is a skill published in the GitHub repository davekilleen/Dex (507 stars, last pushed yesterday), licensed MIT. It adds 32 tokens to every session and 1,144 once invoked, about $0.0001 per session on Opus 5.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
debugging-strategies
Master systematic debugging techniques, profiling tools, and root cause analysis to efficiently track down bugs across any codebase or technology stack. Use when investigating bugs, performance issues, or unexpected behavior.
git-advanced-workflows
Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.
sql-optimization-patterns
Master SQL query optimization, indexing strategies, and EXPLAIN analysis to dramatically improve database performance and eliminate slow queries. Use when debugging slow queries, designing database schemas, or optimizing application performance.
parallel-debugging
Debug complex issues using competing hypotheses with parallel investigation, evidence collection, and root cause arbitration. Use this skill when debugging bugs with multiple potential causes, performing root cause analysis, or organizing parallel investigation workflows.
error-handling-patterns
Master error handling patterns across languages including exceptions, Result types, error propagation, and graceful degradation to build resilient applications. Use when implementing error handling, designing APIs, or improving application reliability.
spark-optimization
Optimize Apache Spark jobs with partitioning, caching, shuffle optimization, and memory tuning. Use when improving Spark performance, debugging slow jobs, or scaling data processing pipelines.