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/alipay-webhooksnpx skills add hookdeck/webhook-skills --skill alipay-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/alipay-webhooks)<a href="https://agentmods.dev/skills/hookdeck/webhook-skills/alipay-webhooks"><img src="https://agentmods.dev/badge/skills/hookdeck/webhook-skills/alipay-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.00058 | $0.02359 |
| Opus 5 | $0.00029 | $0.01179 |
| Sonnet 5 | $0.00012 | $0.00472 |
| Haiku 4.5 | $0.00006 | $0.00236 |
Grade A, and why
alipay-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.
How it starts
The opening of the file, as written. The whole thing — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Alipay Webhooks
Alipay's global / cross-border products — Antom (Cashier Payment / AMS) and
Alipay+ — deliver asynchronous webhook notifications (notifyPayment,
notifyRefund, notifyCapture, notifyAuthorization, notifyDispute) signed
with an asymmetric RSA256 (SHA256withRSA) scheme carried in a Signature
header. This skill targets that header-based scheme.
Legacy note: The older Alipay openapi / MAPI integration (
openapi.alipay.com,global.alipay.com) is a different, unrelated scheme — form-encoded params withsign+sign_type=RSA2, verified by strippingsign/sign_type, sorting the remaining params A–Z, joining with&, and replying with the plain textsuccess. If your integration postsapplication/x-www-form-urlencodedbodies with asignfield, you are on that older vintage — this skill does not cover it. Everything below is the modern Antom/Alipay+ header RSA256 scheme.
When to Use This Skill
- How do I receive Alipay / Antom / Alipay+ webhooks?
- How do I verify the Alipay
Signatureheader (RSA256 / SHA256withRSA)? - How do I handle
notifyPayment,notifyRefund, ornotifyDisputeevents? - Why is my Alipay webhook signature verification failing (base64URL encoding)?
- How do I sign the acknowledgement response Antom expects?
Verification (core)
Alipay/Antom signs each request with SHA256withRSA using its private key and
carries the result in a Signature header. You verify it with Antom's public
key (from the Dashboard). Three details trip people up:
- The signed content is exactly two lines:
<METHOD> <URI>then<Client-Id>.<Request-Time>.<RawBody>joined by single periods. - The signature is base64URL encoded (URL-safe alphabet), and is often additionally percent-encoded on the wire — URL-decode, then base64-decode.
- Use the raw request body — never re-serialize parsed JSON first.
const { createVerify } = require('crypto');
// Header: "algorithm=RSA256,keyVersion=1,signature=<urlEncoded base64url sig>"
function parseSignatureHeader(header) {
return Object.fromEntries(
header.split(',').map((p) => {
const i = p.indexOf('=');
return [p.slice(0, i).trim(), p.slice(i + 1).trim()];
})
);
}
function verifyAlipay({ method, uri, clientId, requestTime, rawBody, signatureHeader, publicKey }) {
const { signature } = parseSignatureHeader(signatureHeader);
if (!signature) return false;
const content = `${method} ${uri}\n${clientId}.${requestTime}.${rawBody}`;
// Percent-decode, normalize URL-safe base64 → standard, then decode.
const sig = Buffer.from(decodeURIComponent(signature).replace(/-/g, '+').replace(/_/g, '/'), 'base64');
const v = createVerify('RSA-SHA256');
v.update(content, 'utf8');
v.end();
try {
return v.verify(publicKey, sig); // publicKey = Antom/Alipay+ PEM public key
} catch {
return false;
}
}
What ships with it
22 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 643 B
- examples/express/package.json 420 B
- examples/express/README.md 2.0 KB
- examples/express/src/index.js 3.9 KB runs code
- examples/express/src/verify.js 3.0 KB runs code
- examples/express/test/webhook.test.js 6.0 KB runs code
- examples/fastapi/.env.example 632 B
- examples/fastapi/main.py 5.8 KB runs code
- examples/fastapi/README.md 2.0 KB
- examples/fastapi/requirements.txt 123 B
- examples/fastapi/test_webhook.py 5.8 KB runs code
- examples/nextjs/.env.example 632 B
- examples/nextjs/app/webhooks/alipay/route.ts 3.2 KB runs code
- examples/nextjs/lib/verify.ts 3.0 KB runs code
- examples/nextjs/package.json 468 B
- examples/nextjs/README.md 1.8 KB
- examples/nextjs/test/webhook.test.ts 5.9 KB runs code
- examples/nextjs/tsconfig.json 562 B
- examples/nextjs/vitest.config.ts 289 B runs code
- references/overview.md 4.0 KB
- references/setup.md 3.6 KB
- references/verification.md 6.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.
- 5d ago First seen · 181 lines · 58 tokens per session scan A 2c5051ccd65f
alipay-webhooks is a skill published in the GitHub repository hookdeck/webhook-skills (84 stars, last pushed yesterday), licensed MIT. It adds 58 tokens to every session and 2,359 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…