incident-response-skill

incident-response-skill is a skill for Claude Code, Codex from agentfront/frontmcp. It costs 24 tokens per session (809 once invoked), scanned A, original, Apache-2.0.

A skill for responding to production incidents by checking service health, searching logs, applying mitigations, and notifying the incident channel.

In plain words
What is it for?
It is for investigating service failures, rolling back deployments, changing service capacity, and sending incident updates.
Why use it?
It gives an agent a defined sequence for diagnosing outages, reducing their impact, and keeping people informed.

Skill for Claude CodeCodex

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 skills/agentfront/frontmcp/incident-response
Any agent
npx skills add agentfront/frontmcp --skill incident-response
Clone the repo
git clone --depth 1 https://github.com/agentfront/frontmcp

Made for: Claude Code, Codex.

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-response-skill

README.md
[![agentmods](https://agentmods.dev/badge/skills/agentfront/frontmcp/incident-response.svg)](https://agentmods.dev/skills/agentfront/frontmcp/incident-response)
Your own site
<a href="https://agentmods.dev/skills/agentfront/frontmcp/incident-response"><img src="https://agentmods.dev/badge/skills/agentfront/frontmcp/incident-response.svg" alt="Measured on agentmods" height="20"></a>
Per session 24 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 809 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. 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.00024 $0.00809
Opus 5 $0.00012 $0.00404
Sonnet 5 $0.00005 $0.00162
Haiku 4.5 $0.00002 $0.00081

Measured yesterday against content hash f2f2d8ab38a8, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

incident-response-skill 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 yesterday.

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.

libs/skills/catalog/frontmcp-development/examples/create-skill-with-tools/incident-response-skill.md · 93 lines

How it starts

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

Incident Response Skill with Detailed Tool Metadata

A skill that uses object-style tool references with purpose descriptions and required flags, plus strict validation.

Code

// src/skills/incident-response.skill.ts
import { Skill, SkillContext } from '@frontmcp/sdk';

@Skill({
  name: 'incident-response',
  description: 'Respond to production incidents',
  instructions: `# Incident Response

## Step 1: Gather Information
Use check_service_health to determine which services are affected.
Use query_logs to find error patterns.

## Step 2: Mitigate
Use rollback_deployment if a recent deploy caused the issue.
Use scale_service if the issue is load-related.

## Step 3: Communicate
Use send_notification to update the incident channel.`,
  tools: [
    { name: 'check_service_health', purpose: 'Check health status of services', required: true },
    { name: 'query_logs', purpose: 'Search application logs for errors', required: true },
    { name: 'rollback_deployment', purpose: 'Rollback to previous deployment', required: false },
    { name: 'scale_service', purpose: 'Scale service replicas up or down', required: false },
    { name: 'send_notification', purpose: 'Send notification to Slack channel', required: true },
  ],
  toolValidation: 'strict', // Fail at startup if any required tool is missing
  parameters: [
    { name: 'severity', description: 'Incident severity level', type: 'string', required: true },
    { name: 'auto-rollback', description: 'Whether to auto-rollback on detection', type: 'boolean', default: false },
  ],
  examples: [
    {
      scenario: 'API latency spike after a deployment',
      expectedOutcome: 'Health checked, logs queried, deployment rolled back, team notified',
    },
  ],
  tags: ['incident', 'ops', 'on-call'],
  visibility: 'mcp',
})
class IncidentResponseSkill extends SkillContext {}
// src/server.ts
import { FrontMcp, App } from '@frontmcp/sdk';

@App({
  name: 'ops-app',
  skills: [IncidentResponseSkill],
  tools: [CheckServiceHealthTool, QueryLogsTool, RollbackDeploymentTool, ScaleServiceTool, SendNotificationTool],
})
class OpsApp {}

@FrontMcp({
  info: { name: 'ops-server', version: '1.0.0' },
  apps: [OpsApp],
})
class OpsServer {}

Read the full file on GitHub · 93 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. yesterday First seen · 93 lines · 24 tokens per session scan A f2f2d8ab38a8

Subscribe to this mod's changes

incident-response-skill is a skill published in the GitHub repository agentfront/frontmcp (146 stars, last pushed 3d ago), licensed Apache-2.0. It adds 24 tokens to every session and 809 once invoked, about $0.0001 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-09-03.

Related

Other skills, from other repositories

a0-development

Development guide for extending Agent Zero from current source and DOX. Use for framework architecture, tools, extensions, API/WebUI handlers, agent profiles, prompts, skills, projects, runtime boundaries, and contribution workflow. Load the focused reference files before giving implementation guidance.

agent0ai/agent-zero · 57 tokens

incident-response

Incident triage, cascade prevention, and postmortem methodology. Use when handling production incidents, designing resilience patterns, or conducting chaos engineering exercises.

NickCrew/Claude-Cortex · 32 tokens

a0-development

Development guide for extending and building features for the Agent Zero AI framework. Covers architecture, tools, extensions, API endpoints, agent profiles, projects, prompts, and skills — with correct paths, imports, and patterns matching the current codebase.

Gen-Verse/PAST-Bench · 52 tokens

incident-response

Incident response runbook for cluster emergencies. Standardized procedure for service outages, security breaches, data corruption, and performance degradation. Includes triage, containment, investigation, resolution, and post-mortem. Use when: (1) Service is down, (2) Security breach detected, (3) Data corruption…

aris4u-dev/aris4u · 74 tokens

agentcore-investigation

Investigate Bedrock AgentCore runtime sessions via CloudWatch Logs Insights — resolve session/trace IDs, query OTEL spans, filter noise, build timelines. Use when debugging AgentCore agent sessions, tracing tool calls, or analyzing latency.

awslabs/mcp · 52 tokens

technical-writing

Write, edit, review, or audit user-facing documentation for the eve repository. Use for changes under docs/, documentation tied to eve APIs or CLI behavior, docs work based on Slack or support feedback, and requests to make eve docs clearer, more natural, or less AI-patterned while verifying claims against current…

vercel/eve · 78 tokens