pagerduty-webhooks

pagerduty-webhooks is a skill for Claude Code, Codex from hookdeck/webhook-skills. It costs 192 tokens per session (6,724 once invoked), scanned A, original, MIT.

A guide for receiving and checking PagerDuty V3 webhooks, which are HTTP messages sent when incidents or services change. It also explains how V3 differs from older webhook extensions and PagerDuty's alert-sending API.

In plain words
What is it for?
Use it to create a PagerDuty webhook handler, verify signed request bodies, and process incident and service changes.
Why use it?
It helps developers use the supported webhook format and avoid applying V3 signature checks to incompatible legacy requests.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to create a PagerDuty webhook handler, verify signed request bodies, and process incident and service changes.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/hookdeck/webhook-skills/pagerduty-webhooks
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 hookdeck/webhook-skills --skill pagerduty-webhooks
Clone the repo
git clone --depth 1 https://github.com/hookdeck/webhook-skills

Made for: Claude Code, Codex.

Its marketplace also offers this one on its own, as the plugin pagerduty-webhooks — /plugin install pagerduty-webhooks after adding the marketplace above.

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

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/hookdeck/webhook-skills/pagerduty-webhooks"><img src="https://agentmods.dev/badge/skills/hookdeck/webhook-skills/pagerduty-webhooks.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 192 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 6,724 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00192 $0.06724
Opus 5.5 $0.00077 $0.02690
Sonnet 5.5 $0.00038 $0.01345
Haiku 4.5 $0.00019 $0.00672

Measured 13d ago against content hash 880aa2776635, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

pagerduty-webhooks 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 13d ago.

The scan reads SKILL.md. This mod also ships 7 executable files (examples/express/src/index.js, examples/express/test/webhook.test.js, examples/fastapi/main.py, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

curl -X POST https://api.pagerduty.com/webhook_subscriptions \
skills/pagerduty-webhooks/SKILL.md · 471 lines

How it starts

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

PagerDuty Webhooks

PagerDuty sends outbound V3 webhooks when incidents and services change — triggered, acknowledged, escalated, reassigned, resolved, annotated, and more.

This skill targets V3 webhook subscriptions — the current and only supported generation, created via POST https://api.pagerduty.com/webhook_subscriptions.

Canonical docs: Webhooks Overview, Verifying Signatures, Behaviour.

What This Is Not

  • V1 webhook extensions — not covered, EOL October 2022 (they no longer function).
  • V2 webhook extensions — legacy. End-of-support 31 Oct 2022, still functioning (no EOL date set) but receiving no fixes or features. Their payload is a messages[] array with event strings like incident.trigger (singular, no d) — deliberately different from V3's incident.triggered. V2 extensions are not signed with X-PagerDuty-Signature, so none of the verification here applies to them. Migrate to V3.
  • PagerDuty Events API v1/v2 (events.pagerduty.com) — the opposite direction. You send alerts and change events to PagerDuty. Not webhooks.
  • Custom Incident Actions / "Generic Webhooks" — same delivery pipeline, but a 16-second response timeout instead of 5 (see Delivery).
  • Lookalikes: PagerTree, Pagerly, Opsgenie, incident.io. Unrelated companies.

When to Use This Skill

  • How do I receive PagerDuty webhooks?
  • How do I verify a PagerDuty webhook signature?
  • Why is my X-PagerDuty-Signature verification failing?
  • Why does X-PagerDuty-Signature contain two signatures?
  • How do I handle incident.triggered, incident.acknowledged and incident.resolved?
  • Where do I get the PagerDuty webhook signing secret?
  • Does PagerDuty send a handshake or validation request? (No.)
  • How do I de-duplicate PagerDuty webhook retries?

Read the full file on GitHub · 471 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. 13d ago First seen · 471 lines · 192 tokens per session scan A 880aa2776635

Subscribe to this mod's changes

pagerduty-webhooks is a skill published in the GitHub repository hookdeck/webhook-skills (92 stars, last pushed 3d ago), licensed MIT. It adds 192 tokens to every session and 6,724 once invoked, about $0.0008 per session on Opus 5.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-10-03.

Related

Other skills, from other repositories

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

systematic-debugging

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

obra/superpowers · 21 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