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/adyen-webhooksnpx skills add hookdeck/webhook-skills --skill adyen-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/adyen-webhooks)<a href="https://agentmods.dev/skills/hookdeck/webhook-skills/adyen-webhooks"><img src="https://agentmods.dev/badge/skills/hookdeck/webhook-skills/adyen-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.00057 | $0.01990 |
| Opus 5 | $0.00028 | $0.00995 |
| Sonnet 5 | $0.00011 | $0.00398 |
| Haiku 4.5 | $0.00006 | $0.00199 |
Grade A, and why
adyen-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.
Copies of this mod
8 near-identical copies found in the catalogue:
- flexport-webhooks — 89% identical, 192 lines differ
- discord-webhooks — 88% identical, 274 lines differ
- fusionauth-webhooks — 86% identical, 252 lines differ
- bunny-stream-webhooks — 86% identical, 181 lines differ
- chargebee-webhooks — 86% identical, 281 lines differ
- cursor-webhooks — 84% identical, 243 lines differ
- fastspring-webhooks — 84% identical, 170 lines differ
- gitlab-webhooks — 84% identical, 213 lines differ
How it starts
The opening of the file, as written. The whole thing — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Adyen Webhooks
When to Use This Skill
- How do I receive Adyen webhooks (standard notifications)?
- How do I verify Adyen webhook HMAC signatures?
- How do I handle AUTHORISATION, CAPTURE, REFUND, or CHARGEBACK events?
- Why is my Adyen HMAC signature verification failing?
- What response body does Adyen expect from my webhook endpoint?
How Adyen Webhooks Work
Adyen sends standard notifications as an HTTP POST with a JSON body containing
a batch of notificationItems. Each item wraps a NotificationRequestItem:
{
"live": "false",
"notificationItems": [
{
"NotificationRequestItem": {
"eventCode": "AUTHORISATION",
"success": "true",
"pspReference": "7914073381342284",
"merchantAccountCode": "TestMerchant",
"merchantReference": "TestPayment-1407325143704",
"amount": { "value": 1130, "currency": "EUR" },
"additionalData": { "hmacSignature": "coqCmt/IZ4E3CzPvMY8zTjQVL5hYJUiBRg8UU+iCWo0=" }
}
}
]
}
Your endpoint must:
- Verify the HMAC signature on each item (
additionalData.hmacSignature). - Acknowledge with the literal body
[accepted]and HTTP 200 — otherwise Adyen retries.
Verification (core)
Adyen's HMAC is not computed over the raw request body. It is computed over a
:-delimited string of specific fields, in this exact order:
pspReference : originalReference : merchantAccountCode : merchantReference : amount.value : amount.currency : eventCode : success
Each field value is escaped (\ → \\, : → \:), empty fields become empty
strings, and the HMAC key from the Customer Area is a hex string that must be
hex-decoded before use. The result is HMAC-SHA256, base64-encoded, and compared
against additionalData.hmacSignature. Because the signature covers parsed fields,
you parse the JSON first, then verify each item.
The official @adyen/api-library SDK does all of this for you:
const { hmacValidator } = require('@adyen/api-library');
const validator = new hmacValidator();
// item = notificationItems[i].NotificationRequestItem (plain parsed object)
// ADYEN_HMAC_KEY = hex string from the Customer Area
const valid = validator.validateHMAC(item, process.env.ADYEN_HMAC_KEY);
// reads item.additionalData.hmacSignature and compares (timing-safe) internally
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 383 B
- examples/express/package.json 403 B
- examples/express/README.md 1.8 KB
- examples/express/src/index.js 5.0 KB runs code
- examples/express/test/webhook.test.js 6.0 KB runs code
- examples/fastapi/.env.example 383 B
- examples/fastapi/main.py 5.7 KB runs code
- examples/fastapi/README.md 2.1 KB
- examples/fastapi/requirements.txt 82 B
- examples/fastapi/test_webhook.py 4.7 KB runs code
- examples/nextjs/.env.example 383 B
- examples/nextjs/app/webhooks/adyen/route.ts 4.4 KB runs code
- examples/nextjs/package.json 514 B
- examples/nextjs/README.md 1.8 KB
- examples/nextjs/test/webhook.test.ts 4.7 KB runs code
- examples/nextjs/vitest.config.ts 140 B runs code
- references/overview.md 4.2 KB
- references/setup.md 3.1 KB
- references/verification.md 5.6 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 · 175 lines · 57 tokens per session scan A 8f002fe7791e
adyen-webhooks is a skill published in the GitHub repository hookdeck/webhook-skills (84 stars, last pushed 7d ago), licensed MIT. It adds 57 tokens to every session and 1,990 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…