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/paypro-global-webhooksnpx skills add hookdeck/webhook-skills --skill paypro-global-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/paypro-global-webhooks)<a href="https://agentmods.dev/skills/hookdeck/webhook-skills/paypro-global-webhooks"><img src="https://agentmods.dev/badge/skills/hookdeck/webhook-skills/paypro-global-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.00087 | $0.02002 |
| Opus 5 | $0.00044 | $0.01001 |
| Sonnet 5 | $0.00017 | $0.00400 |
| Haiku 4.5 | $0.00009 | $0.00200 |
Grade A, and why
paypro-global-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.
This is a copy
83% identical to adyen-webhooks — 181 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 — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PayPro Global Webhooks (IPN)
PayPro Global calls its webhooks IPN — Instant Payment Notification. When
an order or subscription event occurs, PayPro Global sends an HTTP POST with
a application/x-www-form-urlencoded body (not JSON) to the IPN URL you
configure. Verification is bespoke: it is not HMAC-in-a-header and not
Standard Webhooks.
When to Use This Skill
- How do I receive PayPro Global IPN webhooks?
- How do I verify the PayPro Global
SIGNATURE(SHA256) parameter? - How do I verify the PayPro Global
HASH(MD5) parameter? - Why is my PayPro Global signature verification failing?
- How do I handle
OrderCharged,OrderRefunded, orSubscriptionChargeSucceedevents? - How do I restrict IPN requests to PayPro Global's IP addresses?
Verification (core)
PayPro Global has three independent layers — verify all that you can:
- IP allowlist — requests come only from fixed PayPro Global IPs
(IPv4
198.199.123.239,157.230.8.40; IPv62604:a880:400:d0::1843:7001,2604:a880:400:d1::b6c:c001). SIGNATURE—SHA256(hex) over seven field values concatenated in this exact order:ORDER_ID+ORDER_STATUS+ORDER_TOTAL_AMOUNT+CUSTOMER_EMAIL+VALIDATION_KEY+TEST_MODE+IPN_TYPE_NAME.HASH—MD5ofORDER_ID+SecretKeyfor real orders, orMD5("1")for test orders.
VALIDATION_KEY(for SIGNATURE) andSecretKey(for HASH) are two different keys. Both live under Store Settings → General Settings → Integration. Mixing them up is the most common verification bug.
The signature covers specific field values, not the raw request body — so parsing the form first is correct here (unlike HMAC-over-raw-body providers). Recompute server-side and compare timing-safely (Node):
const crypto = require('crypto');
// SIGNATURE = SHA256(ORDER_ID + ORDER_STATUS + ORDER_TOTAL_AMOUNT +
// CUSTOMER_EMAIL + VALIDATION_KEY + TEST_MODE + IPN_TYPE_NAME). Order and the
// inclusion of TEST_MODE + IPN_TYPE_NAME are easy to get wrong — keep them exact.
function verifySignature(f, validationKey) {
const base = `${f.ORDER_ID ?? ''}${f.ORDER_STATUS ?? ''}${f.ORDER_TOTAL_AMOUNT ?? ''}` +
`${f.CUSTOMER_EMAIL ?? ''}${validationKey}${f.TEST_MODE ?? ''}${f.IPN_TYPE_NAME ?? ''}`;
const expected = crypto.createHash('sha256').update(base, 'utf8').digest('hex');
const a = Buffer.from(expected);
const b = Buffer.from(String(f.SIGNATURE ?? '').toLowerCase());
return a.length === b.length && crypto.timingSafeEqual(a, b);
}
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 580 B
- examples/express/package.json 386 B
- examples/express/README.md 2.1 KB
- examples/express/src/index.js 6.1 KB runs code
- examples/express/test/webhook.test.js 4.7 KB runs code
- examples/fastapi/.env.example 606 B
- examples/fastapi/main.py 5.2 KB runs code
- examples/fastapi/README.md 2.3 KB
- examples/fastapi/requirements.txt 86 B
- examples/fastapi/test_webhook.py 4.1 KB runs code
- examples/nextjs/.env.example 606 B
- examples/nextjs/app/webhooks/paypro-global/route.ts 5.5 KB runs code
- examples/nextjs/package.json 498 B
- examples/nextjs/README.md 2.2 KB
- examples/nextjs/test/webhook.test.ts 4.9 KB runs code
- examples/nextjs/vitest.config.ts 140 B runs code
- references/overview.md 4.2 KB
- references/setup.md 2.4 KB
- references/verification.md 5.2 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 · 146 lines · 87 tokens per session scan A 578a3c8d1ad3
paypro-global-webhooks is a skill published in the GitHub repository hookdeck/webhook-skills (84 stars, last pushed yesterday), licensed MIT. It adds 87 tokens to every session and 2,002 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 83% identical to adyen-webhooks, differing in 181 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…
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…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…