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/airwallex-webhooksnpx skills add hookdeck/webhook-skills --skill airwallex-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/airwallex-webhooks)<a href="https://agentmods.dev/skills/hookdeck/webhook-skills/airwallex-webhooks"><img src="https://agentmods.dev/badge/skills/hookdeck/webhook-skills/airwallex-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.00070 | $0.01600 |
| Opus 5 | $0.00035 | $0.00800 |
| Sonnet 5 | $0.00014 | $0.00320 |
| Haiku 4.5 | $0.00007 | $0.00160 |
Grade A, and why
airwallex-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.
This is a copy
81% identical to adyen-webhooks — 161 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Airwallex Webhooks
When to Use This Skill
- How do I receive Airwallex webhooks?
- How do I verify Airwallex webhook signatures (
x-signature/x-timestamp)? - How do I handle
payment_intent.succeeded,refund.settled, orpayment_dispute.*events? - Why is my Airwallex webhook signature verification failing?
Verification (core)
Airwallex signs every webhook with HMAC-SHA256. Two headers arrive with each request:
x-timestamp— the send time as a Unix timestamp in millisecondsx-signature— the HMAC-SHA256 hex digest
The signed message is x-timestamp concatenated with the raw request body (timestamp first), keyed with the endpoint's unique secret. There is no Node SDK helper for this — verify manually and always use the original, unmodified raw body. Verify before parsing JSON.
const crypto = require('crypto');
// value_to_digest = x-timestamp + raw_body (timestamp first, then the raw bytes)
function verifyAirwallexSignature(rawBody, timestamp, signature, secret) {
if (!timestamp || !signature) return false;
const expected = crypto
.createHmac('sha256', secret)
.update(timestamp) // string, e.g. "1712345678000"
.update(rawBody) // raw request body Buffer/bytes — never re-serialized JSON
.digest('hex');
const a = Buffer.from(expected, 'utf8');
const b = Buffer.from(signature, 'utf8');
return a.length === b.length && crypto.timingSafeEqual(a, b); // constant-time compare
}
For complete handlers with route wiring, event dispatch, and tests, see:
Common Event Types
Airwallex event types are dot-namespaced. The event type is in the payload's name field (not type); the resource is in data.object.
| Event | Triggered When |
|---|---|
payment_intent.succeeded |
A PaymentIntent is fully paid |
payment_intent.requires_payment_method |
A payment attempt failed; a new method is needed |
payment_attempt.authorized |
A payment attempt is authorized |
payment_attempt.paid |
A payment attempt is captured/paid |
refund.settled |
A refund has settled to the customer |
refund.failed |
A refund failed |
payment_consent.verified |
A payment consent (for recurring/MIT) is verified |
payment_dispute.requires_response |
A dispute needs evidence submitted |
payment_dispute.won / payment_dispute.lost |
A dispute is resolved |
What ships with it
20 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 238 B
- examples/express/package.json 374 B
- examples/express/README.md 1.7 KB
- examples/express/src/index.js 4.2 KB runs code
- examples/express/test/webhook.test.js 4.4 KB runs code
- examples/fastapi/.env.example 178 B
- examples/fastapi/main.py 3.5 KB runs code
- examples/fastapi/README.md 1.8 KB
- examples/fastapi/requirements.txt 82 B
- examples/fastapi/test_webhook.py 4.6 KB runs code
- examples/nextjs/.env.example 178 B
- examples/nextjs/app/webhooks/airwallex/route.ts 3.4 KB runs code
- examples/nextjs/package.json 486 B
- examples/nextjs/README.md 1.6 KB
- examples/nextjs/test/webhook.test.ts 3.6 KB runs code
- examples/nextjs/vitest.config.ts 140 B runs code
- references/overview.md 5.3 KB
- references/setup.md 2.3 KB
- references/verification.md 4.6 KB
- TODO.md 1.7 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 · 122 lines · 70 tokens per session scan A c97d3186fc76
airwallex-webhooks is a skill published in the GitHub repository hookdeck/webhook-skills (84 stars, last pushed today), licensed MIT. It adds 70 tokens to every session and 1,600 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 81% identical to adyen-webhooks, differing in 161 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…