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/customerio-webhooksnpx skills add hookdeck/webhook-skills --skill customerio-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/customerio-webhooks)<a href="https://agentmods.dev/skills/hookdeck/webhook-skills/customerio-webhooks"><img src="https://agentmods.dev/badge/skills/hookdeck/webhook-skills/customerio-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.00060 | $0.01800 |
| Opus 5 | $0.00030 | $0.00900 |
| Sonnet 5 | $0.00012 | $0.00360 |
| Haiku 4.5 | $0.00006 | $0.00180 |
Grade A, and why
customerio-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 3d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- ebay-webhooks — 86% identical, 162 lines differ
How it starts
The opening of the file, as written. The whole thing — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Customer.io Webhooks
When to Use This Skill
- How do I receive Customer.io Reporting Webhooks?
- How do I verify Customer.io webhook signatures (
X-CIO-Signature)? - How do I handle
emaildelivered,opened,clicked, orbouncedevents? - Why is my Customer.io webhook signature verification failing?
- How do I identify events by
object_type+metricinstead of a dotted name?
How Customer.io Webhooks Are Different
- No single event-name string. Each POST is one event object. Identify it by the
object_type(customer,email,push,sms,in_app,slack,webhook,whatsapp) plus themetric(sent,delivered,opened,clicked,bounced,dropped,spammed,failed,converted,unsubscribed, …). There is noemail.openedfield — you build that pair yourself fromobject_type+metric. - Custom signature scheme (not Standard Webhooks). The signed string is
v0:<X-CIO-Timestamp>:<raw body>, HMAC-SHA256, hex digest. There are nowebhook-id/webhook-signatureheaders. - No verification SDK.
customerio-nodeand thecustomeriopip package are API clients only — they do not ship webhook signature helpers. Verify manually (shown below). - Strict 4-second timeout. Return
2xxwithin 4 seconds or Customer.io retries with exponential backoff for 7 days and backlogs later events. Do heavy work asynchronously.
Verification (core)
Build the string v0:<X-CIO-Timestamp>:<raw body> (version is always v0), HMAC-SHA256 it
with your webhook signing key, and hex-compare against X-CIO-Signature. Use the raw,
unmodified body — don't JSON.parse first.
const crypto = require('crypto');
function verifyCustomerIoWebhook(rawBody, timestamp, signature, signingKey) {
if (!timestamp || !signature) return false;
// Signed content: "v0:<timestamp>:<raw body>". Feed the raw body straight
// into the HMAC so it is never re-encoded.
const hmac = crypto.createHmac('sha256', signingKey);
hmac.update(`v0:${timestamp}:`);
hmac.update(rawBody); // Buffer or string of the unmodified request body
const expected = hmac.digest('hex');
try {
return crypto.timingSafeEqual(
Buffer.from(signature, 'hex'),
Buffer.from(expected, 'hex')
);
} catch {
return false; // length mismatch / non-hex signature
}
}
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 207 B
- examples/express/package.json 377 B
- examples/express/README.md 1.6 KB
- examples/express/src/index.js 4.8 KB runs code
- examples/express/test/webhook.test.js 6.1 KB runs code
- examples/fastapi/.env.example 138 B
- examples/fastapi/main.py 4.0 KB runs code
- examples/fastapi/README.md 1.6 KB
- examples/fastapi/requirements.txt 82 B
- examples/fastapi/test_webhook.py 5.8 KB runs code
- examples/nextjs/.env.example 138 B
- examples/nextjs/app/webhooks/customerio/route.ts 3.9 KB runs code
- examples/nextjs/package.json 489 B
- examples/nextjs/README.md 1.5 KB
- examples/nextjs/test/webhook.test.ts 4.5 KB runs code
- examples/nextjs/vitest.config.ts 140 B runs code
- references/overview.md 4.5 KB
- references/setup.md 2.3 KB
- references/verification.md 3.9 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.
- 3d ago First seen · 141 lines · 60 tokens per session scan A bf831e676907
customerio-webhooks is a skill published in the GitHub repository hookdeck/webhook-skills (84 stars, last pushed 7d ago), licensed MIT. It adds 60 tokens to every session and 1,800 once invoked, about $0.0003 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…