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/attentive-webhooksnpx skills add hookdeck/webhook-skills --skill attentive-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/attentive-webhooks)<a href="https://agentmods.dev/skills/hookdeck/webhook-skills/attentive-webhooks"><img src="https://agentmods.dev/badge/skills/hookdeck/webhook-skills/attentive-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.00064 | $0.01654 |
| Opus 5 | $0.00032 | $0.00827 |
| Sonnet 5 | $0.00013 | $0.00331 |
| Haiku 4.5 | $0.00006 | $0.00165 |
Grade A, and why
attentive-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 5d 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.
This is a copy
77% identical to adyen-webhooks — 188 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Attentive Webhooks
When to Use This Skill
- How do I receive Attentive webhooks?
- How do I verify Attentive webhook signatures?
- Why is my
x-attentive-hmac-sha256signature verification failing? - How do I handle
sms.subscribed,sms.unsubscribed, oremail.openedevents? - Understanding Attentive event types and payloads
Verification (core)
Attentive signs the raw request body with HMAC-SHA256 keyed on your
per-webhook signing key (called the "client secret" in the dashboard) and
sends the digest, hex-encoded, in the x-attentive-hmac-sha256 header.
There is no timestamp in the signature (Attentive does not use the Standard
Webhooks scheme), so compute the HMAC over the exact raw body and compare
timing-safe. There is no official server-side SDK, so verify manually.
Node:
const crypto = require('crypto');
function verifyAttentiveWebhook(rawBody, signatureHeader, secret) {
if (!signatureHeader) return false;
const expected = crypto.createHmac('sha256', secret).update(rawBody).digest('hex');
try {
return crypto.timingSafeEqual(
Buffer.from(signatureHeader, 'hex'),
Buffer.from(expected, 'hex')
);
} catch {
return false; // wrong length / non-hex input
}
}
Python:
import hmac, hashlib
def verify_attentive_webhook(raw_body: bytes, signature_header: str, secret: str) -> bool:
if not signature_header:
return False
expected = hmac.new(secret.encode("utf-8"), raw_body, hashlib.sha256).hexdigest()
return hmac.compare_digest(expected, signature_header)
For complete handlers with route wiring, event dispatch, and tests, see:
Common Event Types
The event name is in the payload's type field (Attentive does not send an
event-type header — only the signature header).
| Event | Triggered When |
|---|---|
sms.subscribed |
Subscriber joins an SMS list |
sms.unsubscribed |
Subscriber opts out of SMS |
sms.sent |
An SMS message is sent to a subscriber |
sms.inbound_message |
A subscriber replies via SMS |
sms.message_link_click |
Subscriber clicks a link in an SMS |
email.subscribed |
Subscriber joins an email list |
email.unsubscribed |
Subscriber opts out of email |
email.sent |
An email is sent to a subscriber |
email.opened |
Subscriber opens an email |
email.message_link_click |
Subscriber clicks a link in an email |
custom_attribute.set |
A custom attribute is set on a subscriber |
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 123 B
- examples/express/package.json 374 B
- examples/express/README.md 1003 B
- examples/express/src/index.js 4.4 KB runs code
- examples/express/test/webhook.test.js 5.5 KB runs code
- examples/fastapi/.env.example 123 B
- examples/fastapi/main.py 3.9 KB runs code
- examples/fastapi/README.md 1.1 KB
- examples/fastapi/requirements.txt 82 B
- examples/fastapi/test_webhook.py 5.5 KB runs code
- examples/nextjs/.env.example 123 B
- examples/nextjs/app/webhooks/attentive/route.ts 3.6 KB runs code
- examples/nextjs/package.json 486 B
- examples/nextjs/README.md 914 B
- examples/nextjs/test/webhook.test.ts 3.5 KB runs code
- examples/nextjs/vitest.config.ts 140 B runs code
- references/overview.md 3.5 KB
- references/setup.md 2.6 KB
- references/verification.md 4.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.
- 5d ago First seen · 157 lines · 64 tokens per session scan A 8a6a4a55d4ad
attentive-webhooks is a skill published in the GitHub repository hookdeck/webhook-skills (84 stars, last pushed yesterday), licensed MIT. It adds 64 tokens to every session and 1,654 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 77% identical to adyen-webhooks, differing in 188 lines, and is treated as a copy.
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…