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.
npx skills add hookdeck/webhook-skills --skill sentry-webhooksgit clone --depth 1 https://github.com/hookdeck/webhook-skillsWrote 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.
[](https://agentmods.dev/skills/hookdeck/webhook-skills/sentry-webhooks)<a href="https://agentmods.dev/skills/hookdeck/webhook-skills/sentry-webhooks"><img src="https://agentmods.dev/badge/skills/hookdeck/webhook-skills/sentry-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.
<a href="https://agentmods.dev/skills/hookdeck/webhook-skills/sentry-webhooks"><img src="https://agentmods.dev/badge/skills/hookdeck/webhook-skills/sentry-webhooks.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00184 | $0.05865 |
| Opus 5.5 | $0.00074 | $0.02346 |
| Sonnet 5.5 | $0.00037 | $0.01173 |
| Haiku 4.5 | $0.00018 | $0.00587 |
Grade A, and why
sentry-webhooks 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 14d 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.
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.
How it starts
The opening of the file, as written. The whole thing — 388 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sentry Webhooks
Sentry (sentry.io) is the error-monitoring and application-performance platform. This skill covers Sentry's Integration Platform webhooks — the webhooks emitted by a Sentry internal integration (org-scoped, the common case) or public integration, configured under Settings → Developer Settings.
Canonical docs: Webhooks and Sentry Hook Signature.
Self-hosted Sentry runs the same code, so the scheme below is identical on a self-hosted host — only the domain changes.
Not Sentry Insurance (sentry.com), not the Sentry login/identity products, and not
@sentry/*SDK ingest — events POSTed to Sentry at/api/{project}/store/go the other direction and authenticate with DSN keys, not HMAC. None of this applies there.
When to Use This Skill
- How do I receive Sentry webhooks?
- How do I verify a Sentry webhook signature?
- Why is my
Sentry-Hook-Signatureverification failing? - What is
Sentry-App-Signatureand why do I get it on some requests? - How do I know which event a Sentry webhook is — there's no
typefield? - How do I handle
issue.created,issue.resolvedorissue.ignored? - How do I handle
event_alert.triggeredandmetric_alert.critical? - Does Sentry retry a failed webhook? Why did Sentry disable my webhook?
- What's the difference between Integration Platform webhooks, service hooks and the legacy WebHooks plugin?
The Single Most Important Routing Fact
The resource is only in the Sentry-Hook-Resource header. The JSON body
has no type and no event field — only action. To recover the event
token you must combine them:
event = request.headers['sentry-hook-resource'] + '.' + body.action
// e.g. 'issue' + '.' + 'created' → 'issue.created'
Any handler that switches on a body field alone is wrong and will never fire.
What ships with it
19 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- examples/express/.env.example 1.1 KB
- examples/express/package.json 535 B
- examples/express/README.md 5.8 KB
- examples/express/src/index.js 19 KB runs code
- examples/express/test/webhook.test.js 20 KB runs code
- examples/fastapi/.env.example 1.1 KB
- examples/fastapi/main.py 14 KB runs code
- examples/fastapi/README.md 3.9 KB
- examples/fastapi/requirements.txt 82 B
- examples/fastapi/test_webhook.py 12 KB runs code
- examples/nextjs/.env.example 1.0 KB
- examples/nextjs/app/webhooks/sentry/route.ts 16 KB runs code
- examples/nextjs/package.json 613 B
- examples/nextjs/README.md 3.9 KB
- examples/nextjs/test/webhook.test.ts 12 KB runs code
- examples/nextjs/vitest.config.ts 162 B runs code
- references/overview.md 15 KB
- references/setup.md 9.3 KB
- references/verification.md 12 KB
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.
- 14d ago First seen · 388 lines · 184 tokens per session scan A 11aa8b88cf59
sentry-webhooks is a skill published in the GitHub repository hookdeck/webhook-skills (92 stars, last pushed yesterday), licensed MIT. It adds 184 tokens to every session and 5,865 once invoked, about $0.0007 per session on Opus 5.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-10-03.
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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.
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…
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…