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/courier-webhooksnpx skills add hookdeck/webhook-skills --skill courier-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/courier-webhooks)<a href="https://agentmods.dev/skills/hookdeck/webhook-skills/courier-webhooks"><img src="https://agentmods.dev/badge/skills/hookdeck/webhook-skills/courier-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.00047 | $0.01798 |
| Opus 5 | $0.00023 | $0.00899 |
| Sonnet 5 | $0.00009 | $0.00360 |
| Haiku 4.5 | $0.00005 | $0.00180 |
Grade A, and why
courier-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 4d 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 — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Courier Webhooks
When to Use This Skill
- How do I receive Courier outbound webhooks?
- How do I verify the Courier
courier-signatureheader? - How do I handle
message:updatedstatus changes ornotification:submittedevents? - Why is my Courier webhook signature verification failing?
Verification (core)
Courier signs every outbound webhook with HMAC-SHA256. The courier-signature
header carries a timestamp and hex signature: t=<timestamp>,signature=<hex_digest>.
The signed content is `${timestamp}.${rawBody}` — the timestamp, a literal dot,
then the raw request body (do not JSON.parse before verifying). Courier has no
webhook-verification SDK, so verify manually and compare in constant time.
Courier does not document whether t is in seconds or milliseconds, so normalize it
before the staleness comparison instead of assuming a unit. The 5-minute tolerance
below is this skill's default, not a window Courier publishes — tune it to your needs.
const crypto = require('crypto');
// The unit of `t` is not documented. A ~10-digit value is seconds, a ~13-digit
// value is milliseconds — normalize to ms either way.
function toMillis(timestamp) {
const value = Number(timestamp);
if (!Number.isFinite(value)) return NaN;
return Math.abs(value) < 1e11 ? value * 1000 : value;
}
function verifyCourierWebhook(rawBody, signatureHeader, secret, toleranceMs = 5 * 60 * 1000) {
if (!signatureHeader) return false;
const parts = {};
for (const segment of signatureHeader.split(',')) {
const i = segment.indexOf('=');
if (i !== -1) parts[segment.slice(0, i).trim()] = segment.slice(i + 1).trim();
}
const { t: timestamp, signature } = parts;
if (!timestamp || !signature) return false;
// Reject stale deliveries (accepts a seconds or milliseconds timestamp)
const ts = toMillis(timestamp);
if (!Number.isFinite(ts) || Math.abs(Date.now() - ts) > toleranceMs) return false;
const expected = crypto
.createHmac('sha256', secret)
.update(`${timestamp}.${rawBody}`) // timestamp + "." + raw body
.digest('hex'); // raw body, not JSON.stringify — see references/verification.md
try {
return crypto.timingSafeEqual(Buffer.from(signature, 'hex'), Buffer.from(expected, 'hex'));
} catch {
return false; // length mismatch = invalid
}
}
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 202 B
- examples/express/package.json 370 B
- examples/express/README.md 1.4 KB
- examples/express/src/index.js 5.9 KB runs code
- examples/express/test/webhook.test.js 6.3 KB runs code
- examples/fastapi/.env.example 133 B
- examples/fastapi/main.py 5.1 KB runs code
- examples/fastapi/README.md 1.6 KB
- examples/fastapi/requirements.txt 82 B
- examples/fastapi/test_webhook.py 6.6 KB runs code
- examples/nextjs/.env.example 133 B
- examples/nextjs/app/webhooks/courier/route.ts 4.8 KB runs code
- examples/nextjs/package.json 482 B
- examples/nextjs/README.md 1.5 KB
- examples/nextjs/test/webhook.test.ts 4.9 KB runs code
- examples/nextjs/vitest.config.ts 140 B runs code
- references/overview.md 3.6 KB
- references/setup.md 2.4 KB
- references/verification.md 8.3 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.
- 4d ago First seen · 158 lines · 47 tokens per session scan A 6c20f5f15460
courier-webhooks is a skill published in the GitHub repository hookdeck/webhook-skills (84 stars, last pushed 7d ago), licensed MIT. It adds 47 tokens to every session and 1,798 once invoked, about $0.0002 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-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…