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 skills add hookdeck/webhook-skills --skill tikkie-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/tikkie-webhooks)<a href="https://agentmods.dev/skills/hookdeck/webhook-skills/tikkie-webhooks"><img src="https://agentmods.dev/badge/skills/hookdeck/webhook-skills/tikkie-webhooks/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/hookdeck/webhook-skills/tikkie-webhooks"><img src="https://agentmods.dev/badge/skills/hookdeck/webhook-skills/tikkie-webhooks.svg" alt="Reviewed on agentmods" width="80" 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.00121 | $0.02296 |
| Opus 5.5 | $0.00048 | $0.00918 |
| Sonnet 5.5 | $0.00024 | $0.00459 |
| Haiku 4.5 | $0.00012 | $0.00230 |
Grade A, and why
tikkie-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 8d 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 — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tikkie Webhooks
Tikkie is ABN AMRO's payment-request product. This skill covers notification subscriptions in the Tikkie API v2 (2.3.x):
- Production:
https://api.abnamro.com/v2/tikkie - Sandbox:
https://api-sandbox.abnamro.com/v2/tikkie
Every API call carries an API-Key header (the consumer key from your ABN AMRO
developer portal app) and an X-App-Token header (a UUID app token from the
Tikkie Business Portal).
This skill does not cover ABN AMRO's separate Business Account Notification API (bank-account transaction webhooks) or the retired Tikkie v1 API. Their schemes differ, so don't mix them.
When to Use This Skill
- How do I receive Tikkie payment notifications?
- How do I verify a Tikkie webhook signature? (You can't, because Tikkie doesn't sign them.)
- How do I subscribe to Tikkie notifications (
/paymentrequestssubscription,/transactionssubscription)? - How do I handle
PAYMENT,REFUNDandBUNDLEnotifications? - Why doesn't the Tikkie notification include the amount or status?
Verification (core): there is no signature
The official OpenAPI spec (TikkieAPI_v2.3.yaml) defines only a JSON request
body and a 2XX acknowledgement for notification callbacks. It defines no
signature header, shared secret, HMAC, timestamp header or asymmetric
signature, and ABN AMRO publishes no source-IP allowlist. Do not write
an HMAC verifier for Tikkie. You'd have to invent the inputs, because Tikkie
sends none.
Use these mitigations instead. They reduce risk, but they don't prove who sent the request:
// 1. Weak check: subscriptionId must equal the id returned (201) when you subscribed.
const allowed = process.env.TIKKIE_SUBSCRIPTION_ID.split(',').map((s) => s.trim());
if (!allowed.includes(body.subscriptionId)) return res.status(403).end();
// 2. Strong check: the notification only carries tokens. Re-fetch the real record.
const path = {
PAYMENT: `/paymentrequests/${body.paymentRequestToken}/payments/${body.paymentToken}`,
REFUND: `/paymentrequests/${body.paymentRequestToken}/payments/${body.paymentToken}/refunds/${body.refundToken}`,
BUNDLE: `/transactionbundles/${body.bundleId}`,
}[body.notificationType];
const r = await fetch(`${process.env.TIKKIE_API_BASE_URL}${path}`, {
headers: { 'API-Key': process.env.TIKKIE_API_KEY, 'X-App-Token': process.env.TIKKIE_APP_TOKEN },
});
if (r.status === 404) return res.status(403).end(); // made-up tokens → forged
const record = await r.json(); // amountInCents, status, … come from HERE, never the notification
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 727 B
- examples/express/package.json 391 B
- examples/express/README.md 2.8 KB
- examples/express/src/index.js 8.5 KB runs code
- examples/express/test/webhook.test.js 5.8 KB runs code
- examples/fastapi/.env.example 727 B
- examples/fastapi/main.py 7.2 KB runs code
- examples/fastapi/README.md 3.0 KB
- examples/fastapi/requirements.txt 82 B
- examples/fastapi/test_webhook.py 4.9 KB runs code
- examples/nextjs/.env.example 716 B
- examples/nextjs/app/webhooks/tikkie/route.ts 6.7 KB runs code
- examples/nextjs/package.json 501 B
- examples/nextjs/README.md 2.8 KB
- examples/nextjs/test/webhook.test.ts 5.6 KB runs code
- examples/nextjs/vitest.config.ts 140 B runs code
- references/overview.md 3.8 KB
- references/setup.md 3.2 KB
- references/verification.md 4.1 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.
- 8d ago First seen · 163 lines · 121 tokens per session scan A 753383c282b2
tikkie-webhooks is a skill published in the GitHub repository hookdeck/webhook-skills (92 stars, last pushed yesterday), licensed MIT. It adds 121 tokens to every session and 2,296 once invoked, about $0.0005 per session on Opus 5.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-10-09.
Other skills, from other repositories
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…