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/paystack-webhooksnpx skills add hookdeck/webhook-skills --skill paystack-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/paystack-webhooks)<a href="https://agentmods.dev/skills/hookdeck/webhook-skills/paystack-webhooks"><img src="https://agentmods.dev/badge/skills/hookdeck/webhook-skills/paystack-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.00056 | $0.01632 |
| Opus 5 | $0.00028 | $0.00816 |
| Sonnet 5 | $0.00011 | $0.00326 |
| Haiku 4.5 | $0.00006 | $0.00163 |
Grade A, and why
paystack-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 yesterday.
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
80% identical to adyen-webhooks — 168 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 — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Paystack Webhooks
Paystack is an African payments platform. It notifies your application of payment lifecycle events (charges, transfers, refunds, subscriptions, invoices, disputes) by sending an HTTP POST webhook with a JSON payload to your endpoint.
When to Use This Skill
- How do I receive Paystack webhooks?
- How do I verify the
x-paystack-signatureheader? - Why is my Paystack webhook signature verification failing?
- How do I handle
charge.success,transfer.success, orsubscription.createevents? - Understanding Paystack event types and payload structure
Verification (core)
Paystack signs each webhook with HMAC-SHA512 over the raw request body,
hex-encoded, in the x-paystack-signature header. The key is your Paystack
secret key (sk_test_… / sk_live_…) — the same key you use for API calls.
Verify the raw body — do not JSON.parse before verifying.
The official Paystack SDKs are general API clients with no webhook verification helper, so verify manually. In Node.js (Express, Next.js):
const crypto = require('crypto');
// rawBody: the raw HTTP body as a string/Buffer (NOT parsed JSON)
// signature: value of the x-paystack-signature header
// secret: PAYSTACK_SECRET_KEY (sk_test_… / sk_live_…)
function verifyPaystackWebhook(rawBody, signature, secret) {
if (!signature) return false;
const expected = crypto.createHmac('sha512', secret).update(rawBody).digest('hex');
try {
return crypto.timingSafeEqual(Buffer.from(signature), Buffer.from(expected));
} catch {
return false; // length mismatch → invalid
}
}
In Python (FastAPI):
import hmac, hashlib
expected = hmac.new(secret.encode(), raw_body, hashlib.sha512).hexdigest()
is_valid = hmac.compare_digest(expected, signature_header)
For complete handlers with route wiring, event dispatch, and tests, see:
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 333 B
- examples/express/package.json 372 B
- examples/express/README.md 1.8 KB
- examples/express/src/index.js 4.7 KB runs code
- examples/express/test/webhook.test.js 6.4 KB runs code
- examples/fastapi/.env.example 264 B
- examples/fastapi/main.py 3.9 KB runs code
- examples/fastapi/README.md 1.8 KB
- examples/fastapi/requirements.txt 82 B
- examples/fastapi/test_webhook.py 5.2 KB runs code
- examples/nextjs/.env.example 264 B
- examples/nextjs/app/webhooks/paystack/route.ts 3.8 KB runs code
- examples/nextjs/package.json 485 B
- examples/nextjs/README.md 1.7 KB
- examples/nextjs/test/webhook.test.ts 5.0 KB runs code
- examples/nextjs/tsconfig.json 562 B
- examples/nextjs/vitest.config.ts 140 B runs code
- references/overview.md 4.5 KB
- references/setup.md 2.9 KB
- references/verification.md 4.3 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.
- yesterday First seen · 141 lines · 56 tokens per session scan A 92e46acbba81
paystack-webhooks is a skill published in the GitHub repository hookdeck/webhook-skills (84 stars, last pushed yesterday), licensed MIT. It adds 56 tokens to every session and 1,632 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 80% identical to adyen-webhooks, differing in 168 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.
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…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…