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/wechat-webhooksnpx skills add hookdeck/webhook-skills --skill wechat-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/wechat-webhooks)<a href="https://agentmods.dev/skills/hookdeck/webhook-skills/wechat-webhooks"><img src="https://agentmods.dev/badge/skills/hookdeck/webhook-skills/wechat-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.1 | $0.00075 | $0.02070 |
| Opus 5 | $0.00037 | $0.01035 |
| Sonnet 5 | $0.00015 | $0.00414 |
| Haiku 4.5 | $0.00007 | $0.00207 |
Grade A, and why
wechat-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 2d 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 — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
WeChat Pay Webhooks
When to Use This Skill
- How do I receive WeChat Pay webhooks (APIv3 notifications)?
- How do I verify the
Wechatpay-Signatureheader? - How do I decrypt the encrypted
resourcein a WeChat Pay notification? - How do I handle
TRANSACTION.SUCCESSorREFUND.SUCCESSevents? - Why is my WeChat Pay signature verification failing?
How WeChat Pay Notifications Work
WeChat Pay APIv3 does not use HMAC or the Standard Webhooks spec. Each notification is:
- Asymmetrically signed (SHA256withRSA) — verify with the WeChat Pay platform public key, matched by the
Wechatpay-Serialheader, over the message"{timestamp}\n{nonce}\n{body}\n". - Separately encrypted — the
resourceobject isAEAD_AES_256_GCMciphertext. Decryptresource.ciphertextwith your 32-byte APIv3 key to recover the transaction/refund JSON.
The signed body is the raw request bytes (the ciphertext envelope), so verify first, then decrypt. Always use the raw request body — never JSON.parse before verifying.
Verification (core)
const crypto = require('crypto');
// 0. Select the platform public key by Wechatpay-Serial. WeChat publishes new
// certificates ~24h before signing with them, so an unpinned rotation must
// fail with its own error, not a generic "invalid signature".
const PLATFORM_KEYS = JSON.parse(process.env.WECHAT_PAY_PLATFORM_KEYS || '{}');
function selectPlatformKey(serial) {
const key = PLATFORM_KEYS[serial];
if (!key) {
throw new Error(
`No platform key configured for serial ${serial} — ` +
'fetch the current certs via GET /v3/certificates and add it'
);
}
return key;
}
// 1. Verify the RSA-SHA256 signature over "{timestamp}\n{nonce}\n{body}\n"
function verifySignature(timestamp, nonce, rawBody, signatureB64, platformPublicKey) {
const message = `${timestamp}\n${nonce}\n${rawBody}\n`;
const verifier = crypto.createVerify('RSA-SHA256').update(message, 'utf8');
try {
return verifier.verify(platformPublicKey, signatureB64, 'base64');
} catch {
return false; // malformed key/signature
}
}
// 2. Decrypt resource.ciphertext (AEAD_AES_256_GCM) with your 32-byte APIv3 key
function decryptResource({ ciphertext, nonce, associated_data }, apiV3Key) {
const buf = Buffer.from(ciphertext, 'base64');
const decipher = crypto.createDecipheriv('aes-256-gcm', apiV3Key, nonce);
decipher.setAuthTag(buf.subarray(buf.length - 16)); // last 16 bytes = auth tag
if (associated_data) decipher.setAAD(Buffer.from(associated_data));
const plain = Buffer.concat([decipher.update(buf.subarray(0, -16)), decipher.final()]);
return JSON.parse(plain.toString('utf8'));
}
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 1.1 KB
- examples/express/package.json 372 B
- examples/express/README.md 1.7 KB
- examples/express/src/index.js 6.0 KB runs code
- examples/express/test/webhook.test.js 7.7 KB runs code
- examples/fastapi/.env.example 1023 B
- examples/fastapi/main.py 6.1 KB runs code
- examples/fastapi/README.md 2.0 KB
- examples/fastapi/requirements.txt 103 B
- examples/fastapi/test_webhook.py 8.1 KB runs code
- examples/nextjs/.env.example 1023 B
- examples/nextjs/app/webhooks/wechat/route.ts 5.9 KB runs code
- examples/nextjs/package.json 484 B
- examples/nextjs/README.md 1.6 KB
- examples/nextjs/test/webhook.test.ts 8.1 KB runs code
- examples/nextjs/vitest.config.ts 140 B runs code
- references/overview.md 3.9 KB
- references/setup.md 3.8 KB
- references/verification.md 7.5 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.
- 2d ago First seen · 160 lines · 75 tokens per session scan A 283827d1086d
wechat-webhooks is a skill published in the GitHub repository hookdeck/webhook-skills (84 stars, last pushed 2d ago), licensed MIT. It adds 75 tokens to every session and 2,070 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
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…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…