incident-responder

incident-responder is an agent for Claude Code from heymegabyte/claude-skills. It costs 35 tokens per session (755 once invoked), scanned A, original, no licence file.

An incident-response assistant triggered by Sentry errors. Sentry is a service that records application errors and related debugging information.

In plain words
What is it for?
Use it to inspect error events, trace them to source code, propose a fix, create a branch, and open a pull request.
Why use it?
It helps turn an error report into a code-level investigation and a proposed change, reducing the time spent tracing production failures manually.

Agent for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: model in frontmatter.

Part of the claude-skills plugin — 29 skills, 53 commands, 26 agents shipped together

Good fit Use it to inspect error events, trace them to source code, propose a fix, create a branch, and open a pull request.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/heymegabyte/claude-skills/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/heymegabyte/claude-skills

Made for: Claude Code.

Or install claude-skills, the plugin that ships this one along with the rest of its 29 skills, 53 commands, 26 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/heymegabyte/claude-skills/incident-responder/github.svg)](https://agentmods.dev/agents/heymegabyte/claude-skills/incident-responder)
Your own site
<a href="https://agentmods.dev/agents/heymegabyte/claude-skills/incident-responder"><img src="https://agentmods.dev/badge/agents/heymegabyte/claude-skills/incident-responder/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 incident-responder

Your own site · 80×15
<a href="https://agentmods.dev/agents/heymegabyte/claude-skills/incident-responder"><img src="https://agentmods.dev/badge/agents/heymegabyte/claude-skills/incident-responder.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 35 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 755 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.00035 $0.00755
Opus 5 $0.00017 $0.00378
Sonnet 5 $0.00007 $0.00151
Haiku 4.5 $0.00003 $0.00076

Measured 11d ago against content hash 6cc33b2f9501, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, 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 11d 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 · 82 lines

The source is not reproduced here

A licence we could not identify

The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.

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. 11d ago First seen · 82 lines · 35 tokens per session scan A 6cc33b2f9501

Subscribe to this mod's changes

incident-responder is an agent published in the GitHub repository heymegabyte/claude-skills (21 stars, last pushed 15d ago), with no licence file. It adds 35 tokens to every session and 755 once invoked, about $0.0002 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-30.