investigate-incident

investigate-incident is a skill for Claude Code from Abilityai/abilities. It costs 40 tokens per session (2,031 once invoked), scanned C, original, MIT.

A structured tool for investigating problems in a live production system.

In plain words
What is it for?
It helps collect evidence, classify incident severity, and produce a report with possible root causes.
Why use it?
It organizes evidence from logs, measurements, and databases so the cause and seriousness of an outage are easier to assess.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: names the AskUserQuestion tool.

Part of the utilities plugin — 7 skills shipped together

Good fit It helps collect evidence, classify incident severity, and produce a report with possible root causes.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/abilityai/abilities/investigate-incident
Install

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.

Any agent
npx skills add Abilityai/abilities --skill investigate-incident
Clone the repo
git clone --depth 1 https://github.com/Abilityai/abilities

Made for: Claude Code.

Or install utilities, the plugin that ships this one along with the rest of its 7 skills.

Wrote 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.

agentmods badge for investigate-incident

README.md
[![agentmods](https://agentmods.dev/badge/skills/abilityai/abilities/investigate-incident/github.svg)](https://agentmods.dev/skills/abilityai/abilities/investigate-incident)
Your own site
<a href="https://agentmods.dev/skills/abilityai/abilities/investigate-incident"><img src="https://agentmods.dev/badge/skills/abilityai/abilities/investigate-incident/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.

agentmods 80×15 button for investigate-incident

Your own site · 80×15
<a href="https://agentmods.dev/skills/abilityai/abilities/investigate-incident"><img src="https://agentmods.dev/badge/skills/abilityai/abilities/investigate-incident.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 40 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,031 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 2 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00040 $0.02031
Opus 5.5 $0.00016 $0.00812
Sonnet 5.5 $0.00008 $0.00406
Haiku 4.5 $0.00004 $0.00203

Measured 1mo ago against content hash 3ac502a0cf3f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade C, and why

investigate-incident scanned grade C with 2 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.

Reaches for credential fileshighPrivilege escalation

SSH keys, cloud credentials, git-credentials, .npmrc, /etc/shadow: reading these is how a config file becomes a credential leak.

SSH_KEY=<path to key, default: ~/.ssh/id_rsa>

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

$RUN "curl -s -o /dev/null -w '%{http_code}' http://localhost:$APP_PORT$HEALTH_PATH || echo 'health check failed'"
plugins/utilities/skills/investigate-incident/SKILL.md · 268 lines

How it starts

The opening of the file, as written. The whole thing — 268 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Investigate Incident

ℹ️ First, set expectations: before anything else, print one short line with this skill's version and its most recent change — the top entry of metadata.changelog above — e.g. investigate-incident vX.Y — recent: <summary>. Then proceed.

Conduct a structured investigation of a production incident. Collect evidence systematically, classify severity, and produce a report with root cause hypotheses.


Prerequisites

This skill expects SSH access to the affected system. Configure via environment variables or a local .env file:

SSH_HOST=<ip or hostname>
SSH_USER=<username>
SSH_KEY=<path to key, default: ~/.ssh/id_rsa>
APP_PATH=<path to app on remote, default: ~/app>
COMPOSE_FILE=<docker-compose file, default: docker-compose.yml>

Load connection config:

source .env 2>/dev/null || true
SSH_HOST=${SSH_HOST:-""}
SSH_USER=${SSH_USER:-"ubuntu"}
SSH_KEY=${SSH_KEY:-"~/.ssh/id_rsa"}
APP_PATH=${APP_PATH:-"~/app"}
COMPOSE=${COMPOSE_FILE:-"docker-compose.yml"}
RUN="ssh -i $SSH_KEY $SSH_USER@$SSH_HOST"

If SSH_HOST is empty, check for a scripts/run.sh wrapper and use that instead.


Phase 1: Establish Context

Ask the user (or read from $ARGUMENTS):

  1. What is the reported symptom?
  2. When did it start (approximate time)?
  3. What service or component is affected?
  4. Were any deployments or config changes made recently?

Restate the incident scope before proceeding.


Phase 2: Classify Initial Severity

Use this matrix to set an initial severity (update after evidence):

Severity Criteria
P0 Complete outage — no users can access the system
P1 Major feature broken — significant portion of users affected
P2 Degraded performance or partial feature failure
P3 Minor issue, cosmetic, or affects few users

Phase 3: Collect Evidence

Work through each evidence category. Skip sections that don't apply.

3.1 Service Health

# Container status
$RUN "cd $APP_PATH && docker compose -f $COMPOSE ps"

# Recent restarts
$RUN "cd $APP_PATH && docker compose -f $COMPOSE ps --format json 2>/dev/null | grep -E 'Status|Restarts' || docker compose -f $COMPOSE ps"

Read the full file on GitHub · 268 lines

Changes

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.

  1. 1mo ago First seen · 268 lines · 40 tokens per session scan C 3ac502a0cf3f

Subscribe to this mod's changes

investigate-incident is a skill published in the GitHub repository Abilityai/abilities (12 stars, last pushed 3d ago), licensed MIT. It adds 40 tokens to every session and 2,031 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it C with 2 findings (reaches for credential files, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-07.

Related

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…

ChromeDevTools/chrome-devtools-mcp · 99 tokens

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.

open-metadata/OpenMetadata · 37 tokens

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.

emdash-cms/emdash · 43 tokens

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.

emdash-cms/emdash · 48 tokens

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…

zebbern/claude-code-guide · 71 tokens

deck-retro

Run a fully local agent-deck retrospective over the user's own transcripts, Recall index and logs. Use when a user wants to find recurring failures or take their own finding from investigation through synthetic reproduction, a user-filed issue, a test-first fix and contributor PR handoff. Also use for weekly usage…

asheshgoplani/agent-deck · 86 tokens