An incident-response helper for investigating and responding to production incidents in Rootly, a service for managing operational problems. It runs the investigation separately from the main coding session.

Use it to look up an incident, investigate its context, check service health and responders, and prepare an incident response.

It keeps incident investigation focused and provides fallback commands if the separate investigation process cannot access its tools.

respond — Skill for Claude Code by Rootly-AI-Labs

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 Rootly-AI-Labs/rootly-claude-plugin --skill respond

Clone the repo

git clone --depth 1 https://github.com/Rootly-AI-Labs/rootly-claude-plugin

Made for: Claude Code.

Or install rootly-claude-plugin, the plugin that ships this one along with the rest of its 17 skills, 3 agents, 2 hooks, 1 MCP server.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/rootly-ai-labs/rootly-claude-plugin/respond.svg)](https://agentmods.dev/skills/rootly-ai-labs/rootly-claude-plugin/respond)

Your own site

<a href="https://agentmods.dev/skills/rootly-ai-labs/rootly-claude-plugin/respond"><img src="https://agentmods.dev/badge/skills/rootly-ai-labs/rootly-claude-plugin/respond.svg" alt="Measured on agentmods" height="20"></a>

Per session 61 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,291 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 1 finding. 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.

Model	Per session	Once invoked
Fable 5.1	$0.00061	$0.01291
Opus 5	$0.00030	$0.00646
Sonnet 5	$0.00012	$0.00258
Haiku 4.5	$0.00006	$0.00129

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

Security

Grade A, and why

respond 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 8d 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.

> **Experimental**: this skill uses `context: fork` to delegate to the `incident-investigator` agent. In some Claude Code contexts the forked subagent does not inherit the plugin's MCP tools, in which case the agent will

skills/respond/SKILL.md · 108 lines

How it starts

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

Incident Response (experimental)

Experimental: this skill uses context: fork to delegate to the incident-investigator agent. In some Claude Code contexts the forked subagent does not inherit the plugin's MCP tools, in which case the agent will stop and report rather than fall back to bash/curl. If that happens, use the inline alternatives:

/rootly:brief <incident> — stakeholder summary

/rootly:status — service health

/rootly:oncall — current responders

You are helping the user investigate and respond to a production incident. This runs in a forked context to keep incident data separate from the main coding session.

Workflow

1. Identify the Incident

If $ARGUMENTS contains an incident reference:

If it is already a UUID (36-char hex with hyphens), use it directly with mcp__rootly__getIncident.
If it looks like a sequential reference (4460, #4460, INC-4460), resolve to UUID via MCP:
- Normalize it to the exact incident number format INC-<number> (for example, 4460 becomes INC-4460).
- Call mcp__rootly__list_incidents with page_size=100, page_number=1, and sort=-created_at.
- Scan the returned incidents array for an exact incident_number match. If found, use the corresponding incident_id as the UUID.
- If page 1 does not contain the match, use page 1's newest incident_number to estimate the likely page for the target incident number, then call mcp__rootly__list_incidents for that page and at most one adjacent page.
- On every page, match only on incidents[*].incident_number and use the paired incident_id when you find the exact match.
- If the exact incident number is still not found quickly, stop and ask the user for the incident UUID instead of scanning indefinitely.
Use the resolved UUID for all subsequent MCP calls.
Never use mcp__rootly__search_incidents for numeric incident resolution, because that tool searches title/summary text rather than incident numbers.
Never walk paginated lists indefinitely. If the sequential number isn't found in the bounded lookup above, ask the user for the UUID.

Read the full file on GitHub · 108 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.

8d ago First seen · 108 lines · 61 tokens per session scan A 066d3fb7a7a3

Subscribe to this mod's changes

respond is a skill published in the GitHub repository Rootly-AI-Labs/rootly-claude-plugin (1 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 61 tokens to every session and 1,291 once invoked, about $0.0003 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.

Debugging DevOps and cloud

debug-optimize-lcp

Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…

ChromeDevTools/chrome-devtools-mcp · 99 tokens

systematic-debugging

Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.

open-metadata/OpenMetadata · 37 tokens

diagnose

Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.

emdash-cms/emdash · 43 tokens

repro-admin

Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.

emdash-cms/emdash · 48 tokens

log-error-digest

Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…

zebbern/claude-code-guide · 71 tokens

byted-util-volcengine-detect-retry

An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.

bytedance/agentkit-samples · 101 tokens

respond