customerio-webhooks

customerio-webhooks is a skill for Claude Code, Codex from hookdeck/webhook-skills. It costs 60 tokens per session (1,800 once invoked), scanned A, original, MIT.

A guide for receiving Customer.io reporting notifications, which report messaging results such as emails being delivered, opened, clicked, bounced, or unsubscribed. It explains how to identify the event and verify its signature.

In plain words
What is it for?
Use it to build a reporting webhook handler, verify X-CIO-Signature, and process email, SMS, push, in-app, Slack, WhatsApp, or customer activity reports.
Why use it?
It helps avoid treating forged reports as real and clarifies that Customer.io identifies events with an object type and metric rather than one event-name field.

Skill for Claude CodeCodex

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.

agentmods
npx agentmods add skills/hookdeck/webhook-skills/customerio-webhooks
Any agent
npx skills add hookdeck/webhook-skills --skill customerio-webhooks
Clone the repo
git clone --depth 1 https://github.com/hookdeck/webhook-skills

Made for: Claude Code, Codex.

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

README.md
[![agentmods](https://agentmods.dev/badge/skills/hookdeck/webhook-skills/customerio-webhooks.svg)](https://agentmods.dev/skills/hookdeck/webhook-skills/customerio-webhooks)
Your own site
<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>
Per session 60 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,800 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00060 $0.01800
Opus 5 $0.00030 $0.00900
Sonnet 5 $0.00012 $0.00360
Haiku 4.5 $0.00006 $0.00180

Measured 3d ago against content hash bf831e676907, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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.

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.

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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

skills/customerio-webhooks/SKILL.md · 141 lines

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 email delivered, opened, clicked, or bounced events?
  • Why is my Customer.io webhook signature verification failing?
  • How do I identify events by object_type + metric instead 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 the metric (sent, delivered, opened, clicked, bounced, dropped, spammed, failed, converted, unsubscribed, …). There is no email.opened field — you build that pair yourself from object_type + metric.
  • Custom signature scheme (not Standard Webhooks). The signed string is v0:<X-CIO-Timestamp>:<raw body>, HMAC-SHA256, hex digest. There are no webhook-id / webhook-signature headers.
  • No verification SDK. customerio-node and the customerio pip package are API clients only — they do not ship webhook signature helpers. Verify manually (shown below).
  • Strict 4-second timeout. Return 2xx within 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
  }
}

Read the full file on GitHub · 141 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. 3d ago First seen · 141 lines · 60 tokens per session scan A bf831e676907

Subscribe to this mod's changes

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.

Related

Other skills, from other repositories

systematic-debugging

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

obra/superpowers · 21 tokens

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.

obra/superpowers · 37 tokens

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.

microsoft/vscode · 62 tokens

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.

microsoft/vscode · 51 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