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/mollie-webhooksnpx skills add hookdeck/webhook-skills --skill mollie-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/mollie-webhooks)<a href="https://agentmods.dev/skills/hookdeck/webhook-skills/mollie-webhooks"><img src="https://agentmods.dev/badge/skills/hookdeck/webhook-skills/mollie-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.00082 | $0.01891 |
| Opus 5 | $0.00041 | $0.00945 |
| Sonnet 5 | $0.00016 | $0.00378 |
| Haiku 4.5 | $0.00008 | $0.00189 |
Grade A, and why
mollie-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 — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mollie Webhooks
When to Use This Skill
- Setting up a Mollie webhook handler
- Understanding why Mollie webhooks have no signature to verify
- How do I confirm a Mollie payment status from a webhook?
- Handling payment status changes:
paid,authorized,canceled,expired,failed - Why does my Mollie webhook only contain an
id?
How Mollie Webhooks Work (Read This First)
Mollie webhooks are not signed — there is no HMAC, no signature header, and
no shared secret to verify. Instead of trusting the request, Mollie sends you a
POST with a single application/x-www-form-urlencoded body parameter:
id=tr_5B8cwPMGnU6qLbRvo7qEZo
The status is deliberately not in the payload. You must not trust the
request body — anyone could POST a fake id. Instead you fetch the resource
from the Mollie API using your API key and read the authoritative status. This
is the fetch-to-confirm pattern, and it is the security model: a forged
webhook can only ever cause you to re-fetch a real payment you own.
Mollie ──POST id=tr_xxx──▶ your endpoint
│
▼
GET /v2/payments/tr_xxx (with your API key)
│
▼
read payment.status → act → return 200
Verification (core) — fetch to confirm
There is no signature to check. The "verification" step is fetching the payment
from Mollie's API. Authenticate with your API key as a Bearer token
(test_… or live_…). Always return 200 quickly — even for an unknown or
deleted id — so Mollie stops retrying.
Node (official SDK, @mollie/api-client):
const { createMollieClient } = require('@mollie/api-client');
const mollie = createMollieClient({ apiKey: process.env.MOLLIE_API_KEY });
// req.body.id came from the x-www-form-urlencoded webhook — do NOT trust it as status.
const payment = await mollie.payments.get(req.body.id); // 404 => unknown id, ack with 200
switch (payment.status) { // authoritative status from the API
case 'paid': /* fulfill order */ break;
case 'expired': case 'failed': case 'canceled': /* release order */ break;
}
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 288 B
- examples/express/package.json 437 B
- examples/express/README.md 2.1 KB
- examples/express/src/index.js 3.9 KB runs code
- examples/express/test/webhook.test.js 2.7 KB runs code
- examples/fastapi/.env.example 277 B
- examples/fastapi/main.py 3.7 KB runs code
- examples/fastapi/README.md 2.1 KB
- examples/fastapi/requirements.txt 119 B
- examples/fastapi/test_webhook.py 3.8 KB runs code
- examples/nextjs/.env.example 277 B
- examples/nextjs/app/webhooks/mollie/route.ts 2.9 KB runs code
- examples/nextjs/package.json 559 B
- examples/nextjs/README.md 1.8 KB
- examples/nextjs/test/webhook.test.ts 2.6 KB runs code
- examples/nextjs/vitest.config.ts 140 B runs code
- references/overview.md 2.8 KB
- references/setup.md 2.8 KB
- references/verification.md 4.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.
- 2d ago First seen · 165 lines · 82 tokens per session scan A dc52453c8187
mollie-webhooks is a skill published in the GitHub repository hookdeck/webhook-skills (84 stars, last pushed yesterday), licensed MIT. It adds 82 tokens to every session and 1,891 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…
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…