agentmods.dev

incident-management

incident-management is a skill for Claude Code from confighub/confighub-skills. It costs 52 tokens per session (1,961 once invoked), scanned A, original, MIT.

An incident-response workflow for outages and failing production services managed through ConfigHub. It connects the intended release to the controller and the actual running service.

In plain words
What is it for?
Use it during crashes, outages, or urgent production problems to inspect releases, account for manual cluster changes, apply a scoped mitigation, and close the incident with evidence.
Why use it?
It helps establish which release caused a failure, choose between reverting it and fixing forward, and confirm that the mitigation worked.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the confighub-skills plugin — 16 skills, 1 command, 1 hook shipped together

not rated 2repo changed 2d ago A scan 52 tokens original MIT

Good fit Use it during crashes, outages, or urgent production problems to inspect releases, account for manual cluster changes, apply a scoped mitigation, and close the incident with evidence.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/confighub/confighub-skills/incident-management
View source ↗ confighub/confighub-skills
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 confighub/confighub-skills --skill incident-management
Clone the repo
git clone --depth 1 https://github.com/confighub/confighub-skills

Made for: Claude Code.

Or install confighub-skills, the plugin that ships this one along with the rest of its 16 skills, 1 command, 1 hook.

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-management

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/confighub/confighub-skills/incident-management"><img src="https://agentmods.dev/badge/skills/confighub/confighub-skills/incident-management.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 52 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,961 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 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.00052 $0.01961
Opus 5 $0.00026 $0.00981
Sonnet 5 $0.00010 $0.00392
Haiku 4.5 $0.00005 $0.00196

Measured 2d ago against content hash 83acd0ecb363, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

incident-management 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 2d 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.

skills/incident-management/SKILL.md · 163 lines

How it starts

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

incident-management

Execution mode: follow references/execution-modes.md. This Skill grants no automatic tool permission. Urgency never broadens scope, but in standalone use an explicitly requested mitigation may submit one exact mutation to the host permission system; an external overlay may impose a stricter stop.

Stabilize first, but do not sacrifice attribution. Current delivery evidence is Space Release → OCI manifest → controller → runtime, not retired per-Unit apply status.

First five minutes: establish facts

  1. Bind incident scope: service/resource, namespace, cluster/context, Component, Variant Space, symptom, start time, and incident commander.

  2. Read the newest relevant Releases, then pin the suspect by immutable identity:

    cub release list --space <variant-space> -o json
cub release get --space <variant-space> <release-id>

    Record ReleaseID, creation time, bundle Digest, ManifestDigest, UnitCount, and TagID.

  3. Read the desired/effective ConfigHub set:

    cub space get <variant-space> -o json
cub unit list --space <variant-space> --select "TargetID,HeadRevisionNum,LastReleasedRevisionNum,ValidationErrors" -o json

    To see the affected workload as a resource rather than as a Unit — the faster read when the symptom is phrased in Kubernetes terms — use cub k8s get deploy <name> --space <variant-space> --show detail or --show data. It is configuration, not live state; keep it separate from the kubectl read in step 5.

    If a promotion preceded the symptom, check what its merge withheld as well as what it applied. A merge that could not place part of its patch does not fail — it records the withheld changes on the Unit:

    cub unit conflicts --space <variant-space> <unit>
cub unit list --space <variant-space> --where "Conflicts.*.Reason = 'ProtectedPath'"

    A protected path is the common reason, and the common surprise: an environment-specific value the variant owns held against the release, so the fix that went everywhere else did not land here. cub unit get <unit> -o mutations shows which paths this variant owns. See promote-release for resolving them; resolving is a mutation, not a read.

Read the full file on GitHub · 163 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 2d ago Changed 83acd0ecb363
  2. 12d ago First seen · 163 lines · 52 tokens per session scan A 4e25b3f25433

Subscribe to this mod's changes

incident-management is a skill published in the GitHub repository confighub/confighub-skills (2 stars, last pushed 3d ago), licensed MIT. It adds 52 tokens to every session and 1,961 once invoked, about $0.0003 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.

DevOps and cloud
Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens