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 agentmods add skills/hookdeck/webhook-skills/svix-webhooksnpx skills add hookdeck/webhook-skills --skill svix-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/svix-webhooks)<a href="https://agentmods.dev/skills/hookdeck/webhook-skills/svix-webhooks"><img src="https://agentmods.dev/badge/skills/hookdeck/webhook-skills/svix-webhooks.svg" alt="Measured on agentmods" 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 | $0.00084 | $0.01876 |
| Opus 5 | $0.00042 | $0.00938 |
| Sonnet 5 | $0.00017 | $0.00375 |
| Haiku 4.5 | $0.00008 | $0.00188 |
Grade A, and why
svix-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 yesterday.
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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Svix Webhooks
Svix is webhook-sending infrastructure used by many upstream services. If a provider delivers webhooks "powered by Svix" (or implements the Standard Webhooks spec), the verification below applies regardless of who the sender is.
When to Use This Skill
- How do I receive Svix webhooks?
- How do I verify
svix-id/svix-timestamp/svix-signatureheaders? - Why is my Svix webhook signature verification failing?
- How do I handle secret rotation (multiple
v1,signatures in one header)? - My provider says webhooks are "powered by Svix" / "Standard Webhooks" — how do I verify them?
- How do I parse the
{"type": "...", "data": {...}}event envelope?
Verification (core)
Each request carries three headers:
svix-id: msg_2b1c... # unique message id
svix-timestamp: 1614265330 # Unix seconds
svix-signature: v1,g0hM9SsE... # space-delimited "v1,<base64 sig>" entries
The signed content is ${svix-id}.${svix-timestamp}.${raw_body}, HMAC-SHA256
using the base64-decoded bytes of the secret after the whsec_ prefix, and
the result is base64-encoded. Use the official svix SDK — it handles the
base64 secret, the 5-minute timestamp tolerance, multiple signatures (rotation),
and constant-time comparison for you. Pass the raw body, never re-serialized JSON.
Node:
const { Webhook } = require('svix');
const wh = new Webhook(process.env.SVIX_WEBHOOK_SECRET); // "whsec_..." — SDK decodes it
const event = wh.verify(rawBody, { // rawBody: raw Buffer/string
'svix-id': req.headers['svix-id'],
'svix-timestamp': req.headers['svix-timestamp'],
'svix-signature': req.headers['svix-signature'],
});
// Throws WebhookVerificationError on a bad signature or a timestamp >5 min off.
// The SDK also accepts webhook-id / webhook-timestamp / webhook-signature.
// event => { type: 'invoice.paid', data: { ... } }
Python:
from svix.webhooks import Webhook, WebhookVerificationError
wh = Webhook(os.environ["SVIX_WEBHOOK_SECRET"])
event = wh.verify(raw_body, { # raw_body: bytes of the raw request body
"svix-id": headers["svix-id"],
"svix-timestamp": headers["svix-timestamp"],
"svix-signature": headers["svix-signature"],
}) # raises WebhookVerificationError on failure; returns the parsed {type, data} dict
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 183 B
- examples/express/package.json 480 B
- examples/express/README.md 1.0 KB
- examples/express/src/index.js 2.8 KB runs code
- examples/express/test/webhook.test.js 6.6 KB runs code
- examples/fastapi/.env.example 183 B
- examples/fastapi/main.py 3.1 KB runs code
- examples/fastapi/README.md 1.2 KB
- examples/fastapi/requirements.txt 105 B
- examples/fastapi/test_webhook.py 5.4 KB runs code
- examples/nextjs/.env.example 183 B
- examples/nextjs/app/webhooks/svix/route.ts 2.4 KB runs code
- examples/nextjs/package.json 576 B
- examples/nextjs/README.md 1.1 KB
- examples/nextjs/test/webhook.test.ts 6.2 KB runs code
- examples/nextjs/vitest.config.ts 164 B runs code
- references/overview.md 3.2 KB
- references/setup.md 2.3 KB
- references/verification.md 7.0 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.
- yesterday First seen · 153 lines · 84 tokens per session scan A ba31c6684aa9
svix-webhooks is a skill published in the GitHub repository hookdeck/webhook-skills (84 stars, last pushed yesterday), licensed MIT. It adds 84 tokens to every session and 1,876 once invoked, about $0.0004 per session on Opus 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-09-03.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…