Subagent

PagerDuty Incident Responder

Responds to PagerDuty incidents by analyzing incident context, identifying recent code changes, and suggesting fixes via GitHub PRs.

Type: Subagent
Repository: github/awesome-copilot
GitHub stars: 39.4k
License: MIT
Repo last updated: Sep 27, 2026
Source file: agents/pagerduty-incident-responder.agent.md

What PagerDuty Incident Responder is

PagerDuty Incident Responder is a subagent published in the github/awesome-copilot repository on GitHub, which has about 39.4k stars. The repository describes itself as: “Community-contributed instructions, agents, skills, and configurations to help you make the most of GitHub Copilot.”

A subagent is a specialist assistant that Claude can hand part of a task to. It is a markdown file whose frontmatter sets a name, a description that tells Claude when to delegate, and optionally the tools and model it may use; the body becomes the subagent's own system prompt.

Because a subagent works in its own context, it keeps the main conversation focused: Claude can send a narrow job, such as a review or a specialised analysis, to PagerDuty Incident Responder and get back a compact result.

How to install PagerDuty Incident Responder

Claude Code

Download pagerduty-incident-responder.agent.md from the repository.
Save it to ~/.claude/agents/ to use it in every project, or to .claude/agents/ inside one project to share it through version control.
Claude Code watches these folders, so the subagent is usually available right away. Ask Claude to use it by name, or @-mention it to make sure it runs.

Claude Cowork

Cowork loads subagents through plugins. If the repository is packaged as a plugin marketplace, add it under Customize → Plugins → Add marketplace and install the plugin that contains this subagent.
Otherwise, bundle the file into your own plugin's agents/ folder and upload it from Customize → Plugins.

New to extending Cowork? Our plugins guide and Customize guide explain how skills, plugins, and connectors fit together.

Inside the source file

An excerpt from agents/pagerduty-incident-responder.agent.md, shared under the repository's MIT license. Read the full file on GitHub.

You are a PagerDuty incident response specialist. When given an incident ID or service name:

Retrieve incident details including affected service, timeline, and description using pagerduty mcp tools for all incidents on the given service name or for the specific incident id provided in the github issue
Identify the on-call team and team members responsible for the service
Analyze the incident data and formulate a triage hypothesis: identify likely root cause categories (code change, configuration, dependency, infrastructure), estimate blast radius, and determine which code areas or systems to investigate first
Search GitHub for recent commits, PRs, or deployments to the affected service within the incident timeframe based on your hypothesis
Analyze the code changes that likely caused the incident
Suggest a remediation PR with a fix or rollback

When analyzing incidents:

Search for code changes from 24 hours before incident start time
Compare incident timestamp with deployment times to identify correlation
Focus on files mentioned in error messages and recent dependency updates
Include incident URL, severity, commit SHAs, and tag on-call users in your response
Title fix PRs as "[Incident #ID] Fix for [description]" and link to the PagerDuty incident

If multiple incidents are active, prioritize by urgency level and service criticality. State your confidence level clearly if the root cause is uncertain.

Before you install

Read the whole file first. Skills, commands, and subagents are instructions Claude will follow, so make sure they match what you want.
Check which tools, scripts, or MCP servers it uses. Local servers and scripts run with your permissions.
Try it in a test project or a copy of your files before pointing it at real work.
Pin the version you tested, and review changes before updating.
Watch for instructions that fetch web content or run shell commands; those are where prompt injection risks start. See our prompt injection guide.

FAQ

What is PagerDuty Incident Responder?

PagerDuty Incident Responder is a subagent for Claude Code and Claude Cowork from the github/awesome-copilot repository on GitHub. Responds to PagerDuty incidents by analyzing incident context, identifying recent code changes, and suggesting fixes via GitHub PRs.

How do I install PagerDuty Incident Responder in Claude Code?

Download pagerduty-incident-responder.agent.md from the repository. Save it to ~/.claude/agents/ to use it in every project, or to .claude/agents/ inside one project to share it through version control. Claude Code watches these folders, so the subagent is usually available right away. Ask Claude to use it by name, or @-mention it to make sure it runs.

Can I use PagerDuty Incident Responder in Claude Cowork?

Cowork loads subagents through plugins. If the repository is packaged as a plugin marketplace, add it under Customize → Plugins → Add marketplace and install the plugin that contains this subagent. Otherwise, bundle the file into your own plugin's agents/ folder and upload it from Customize → Plugins.

Is PagerDuty Incident Responder safe to install?

It is a third-party community resource, not reviewed by Anthropic or this site. Read the source file first, check which tools and connectors it uses, and install only from sources you trust.

Similar resources

Browse all skills, subagents, and plugins →

Listing data comes from the public GitHub repository and was last checked in September 2026. Excerpts are © their authors and shared under MIT. This directory is independent and not affiliated with Anthropic or the resource's authors.