incident-responder

incident-responder is an agent for Claude Code from SebastianDevps/agent007. It costs 87 tokens per session (2,040 once invoked), scanned A, original, no licence file.

A commander for serious production incidents, such as outages, security breaches, and other events that affect customers. Production incidents are problems in a live system rather than during development.

In plain words
What is it for?
Coordinating responses to outages, security breaches, severity-one or severity-two events, downtime, and postmortems.
Why use it?
It provides a defined response role when a live service is down, compromised, or experiencing a severe failure.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: model in frontmatter.

Part of the agent007 plugin — 56 skills, 8 commands, 13 agents shipped together

Good fit Coordinating responses to outages, security breaches, severity-one or severity-two events, downtime, and postmortems.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/sebastiandevps/agent007/incident-responder
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.

Clone the repo
git clone --depth 1 https://github.com/SebastianDevps/agent007

Made for: Claude Code.

Or install agent007, the plugin that ships this one along with the rest of its 56 skills, 8 commands, 13 agents.

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/sebastiandevps/agent007/incident-responder.svg)](https://agentmods.dev/agents/sebastiandevps/agent007/incident-responder)
Your own site
<a href="https://agentmods.dev/agents/sebastiandevps/agent007/incident-responder"><img src="https://agentmods.dev/badge/agents/sebastiandevps/agent007/incident-responder.svg" alt="Measured on agentmods" height="20"></a>
Per session 87 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,040 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin unknown 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.00087 $0.02040
Opus 5 $0.00044 $0.01020
Sonnet 5 $0.00017 $0.00408
Haiku 4.5 $0.00009 $0.00204

Measured 7d ago against content hash c34f3cd568a9, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

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

agents/incident-responder.md · 166 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

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. 7d ago First seen · 166 lines · 87 tokens per session scan A c34f3cd568a9

Subscribe to this mod's changes

incident-responder is an agent published in the GitHub repository SebastianDevps/agent007 (5 stars, last pushed 3mo ago), with no licence file. It adds 87 tokens to every session and 2,040 once invoked, about $0.0004 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-31.