pagerduty-incident-responder

pagerduty-incident-responder is an agent for Claude Code from jiamaozheng/awesome-claude-code. It costs 33 tokens per session (478 once invoked), scanned B, original, no licence file.

An incident-response assistant connected to PagerDuty and GitHub for investigating software incidents.

In plain words
What is it for?
Use it to analyze PagerDuty incidents, identify relevant recent changes, and suggest fixes through GitHub pull requests.
Why use it?
It helps relate an active incident to recent code changes, reducing the search for a likely cause.

Agent for Claude Code

Written for Claude Code: a Claude Code subagent (agents/*.md). Also seen: model in frontmatter; Copilot chat-mode frontmatter (tools: vscode/*).

Good fit Use it to analyze PagerDuty incidents, identify relevant recent changes, and suggest fixes through GitHub pull requests.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/jiamaozheng/awesome-claude-code/pagerduty-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/jiamaozheng/awesome-claude-code

Made for: Claude Code.

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 pagerduty-incident-responder

README.md
[![agentmods](https://agentmods.dev/badge/agents/jiamaozheng/awesome-claude-code/pagerduty-incident-responder/github.svg)](https://agentmods.dev/agents/jiamaozheng/awesome-claude-code/pagerduty-incident-responder)
Your own site
<a href="https://agentmods.dev/agents/jiamaozheng/awesome-claude-code/pagerduty-incident-responder"><img src="https://agentmods.dev/badge/agents/jiamaozheng/awesome-claude-code/pagerduty-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 pagerduty-incident-responder

Your own site · 80×15
<a href="https://agentmods.dev/agents/jiamaozheng/awesome-claude-code/pagerduty-incident-responder"><img src="https://agentmods.dev/badge/agents/jiamaozheng/awesome-claude-code/pagerduty-incident-responder.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 33 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 478 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. 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.00033 $0.00478
Opus 5 $0.00016 $0.00239
Sonnet 5 $0.00007 $0.00096
Haiku 4.5 $0.00003 $0.00048

Measured 7d ago against content hash d5425a57d105, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade B, and why

pagerduty-incident-responder scanned grade B 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 7d 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.

Unrestricted tool accessmediumExcessive agency

A wildcard tool grant or "run any command" leaves no least-privilege boundary at all.

tools: ["*"]
agents/pagerduty-incident-responder.md · 35 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

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. 7d ago First seen · 35 lines · 33 tokens per session scan B d5425a57d105

Subscribe to this mod's changes

pagerduty-incident-responder is an agent published in the GitHub repository jiamaozheng/awesome-claude-code (1 stars, last pushed 2d ago), with no licence file. It adds 33 tokens to every session and 478 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (unrestricted tool access). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.