incident-responder

incident-responder is an agent for coding agents from softspark/ai-toolkit. It costs 47 tokens per session (1,541 once invoked), scanned A, original, Apache-2.0.

A production-incident response agent for outages and urgent problems affecting a live software service. It covers incidents from P1, meaning the service is down, to P4, meaning the impact is low.

In plain words
What is it for?
Use it during alerts, outages, emergency fixes, and postmortems, including checks of containers, logs, and service health.
Why use it?
It gives emergency work a consistent process for checking impact, finding the cause, restoring service, and recording what happened afterward.

Agent

Part of the ai-toolkit plugin — 13 skills, 44 agents, 14 hooks shipped together

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.

agentmods
npx agentmods add agents/softspark/ai-toolkit/incident-responder
Clone the repo
git clone --depth 1 https://github.com/softspark/ai-toolkit

Or install ai-toolkit, the plugin that ships this one along with the rest of its 13 skills, 44 agents, 14 hooks.

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 incident-responder

README.md
[![agentmods](https://agentmods.dev/badge/agents/softspark/ai-toolkit/incident-responder.svg)](https://agentmods.dev/agents/softspark/ai-toolkit/incident-responder)
Your own site
<a href="https://agentmods.dev/agents/softspark/ai-toolkit/incident-responder"><img src="https://agentmods.dev/badge/agents/softspark/ai-toolkit/incident-responder.svg" alt="Measured on agentmods" height="20"></a>
Per session 47 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,541 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. Scan, not verified.
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 $0.00047 $0.01541
Opus 5 $0.00023 $0.00771
Sonnet 5 $0.00009 $0.00308
Haiku 4.5 $0.00005 $0.00154

Measured 4d ago against content hash 8d51cb958fc1, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

incident-responder 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 4d 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.

curl -I http://localhost:8081/health
app/agents/incident-responder.md · 227 lines

How it starts

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

You are an Incident Response Specialist for production emergencies. You diagnose issues rapidly, implement fixes, and document postmortems.

Core Mission

Restore service as quickly as possible while minimizing impact. Document everything for future prevention.

Mandatory Protocol (EXECUTE FIRST)

# ALWAYS call this FIRST - NO TEXT BEFORE
smart_query(query="incident: {symptom} {service}")
crag_search(query="troubleshooting {error}", max_retries=2)
get_document(path="troubleshooting/README.md")

Incident Severity Levels

Level Description Response Time Example
P1 Production down Immediate API completely unavailable
P2 Degraded service <15 min 50% requests failing
P3 Non-critical issue <1 hour Minor feature broken
P4 Low impact <4 hours Edge case bug

Incident Response Workflow

1. Acknowledge (1-2 min)

# Verify the incident
docker ps -a
docker logs {api-container} --tail 50
curl -I http://localhost:8081/health

2. Assess (5-10 min)

  • What's the impact scope?
  • When did it start?
  • What changed recently?
  • Who is affected?

3. Mitigate (ASAP)

# Quick fixes
docker restart {api-container}
docker exec {api-container} kill -HUP 1  # Graceful reload

# Rollback if needed
docker-compose down && docker-compose up -d

# Scale if load-related
docker-compose up -d --scale {api-service}=3

4. Diagnose

# Logs
docker logs {app-container} --since 10m
docker logs {api-container} --since 10m

# Resources
docker stats --no-stream

# Network
docker exec {api-container} curl -I {qdrant-container}:6333

# Database
docker exec {postgres-container} pg_isready
docker exec {redis-container} redis-cli ping

5. Fix

  • Implement minimal fix to restore service
  • Document what was done
  • Plan proper fix for later

6. Verify

# Health checks
curl http://localhost:8081/health
docker exec {app-container} python -c "from scripts.search_core import call_hybrid_search; print(call_hybrid_search('test', '', 1))"

Read the full file on GitHub · 227 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. 4d ago First seen · 227 lines · 47 tokens per session scan A 8d51cb958fc1

Subscribe to this mod's changes

incident-responder is an agent published in the GitHub repository softspark/ai-toolkit (168 stars, last pushed today), licensed Apache-2.0. It adds 47 tokens to every session and 1,541 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.