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/tebex-webhooksnpx skills add hookdeck/webhook-skills --skill tebex-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/tebex-webhooks)<a href="https://agentmods.dev/skills/hookdeck/webhook-skills/tebex-webhooks"><img src="https://agentmods.dev/badge/skills/hookdeck/webhook-skills/tebex-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.00055 | $0.01577 |
| Opus 5 | $0.00028 | $0.00788 |
| Sonnet 5 | $0.00011 | $0.00315 |
| Haiku 4.5 | $0.00006 | $0.00158 |
Grade A, and why
tebex-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
86% identical to adyen-webhooks — 170 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 — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tebex Webhooks
When to Use This Skill
- Setting up Tebex webhook handlers
- Debugging Tebex
X-Signatureverification failures - Completing the
validation.webhookhandshake so an endpoint activates - Handling payment, dispute, and recurring-payment events
Verification (core)
Tebex has no SDK. Verify the hex X-Signature header manually. The signature
is two-step: SHA-256 hash the raw request body, then HMAC-SHA256 that
hex hash using your webhook secret as the key. Do not JSON.parse before
verifying — a re-serialized body produces a different hash.
Node:
const crypto = require('crypto');
function verifyTebexSignature(rawBody, signatureHeader, secret) {
const bodyHash = crypto.createHash('sha256').update(rawBody).digest('hex');
const expected = crypto.createHmac('sha256', secret).update(bodyHash).digest('hex');
const received = Buffer.from(signatureHeader || '');
const expectedBuf = Buffer.from(expected);
return received.length === expectedBuf.length &&
crypto.timingSafeEqual(received, expectedBuf);
}
Python:
import hashlib, hmac
def verify_tebex_signature(raw_body: bytes, signature: str, secret: str) -> bool:
body_hash = hashlib.sha256(raw_body).hexdigest()
expected = hmac.new(secret.encode(), body_hash.encode(), hashlib.sha256).hexdigest()
return hmac.compare_digest(expected, signature or "")
Validation handshake: On setup Tebex sends a validation.webhook ping.
After verifying the signature, respond 200 with {"id": "<payload.id>"}
echoing the received id, or the endpoint never activates.
For complete handlers with route wiring, event dispatch, and tests, see:
Common Event Types
| Event | Description |
|---|---|
validation.webhook |
Setup ping — echo the id back with a 200 to activate the endpoint |
payment.completed |
A payment completed successfully |
payment.declined |
A payment was declined |
payment.refunded |
A payment was refunded |
payment.dispute.opened |
A chargeback/dispute was opened |
payment.dispute.won |
A dispute was resolved in your favor |
payment.dispute.lost |
A dispute was resolved against you |
payment.dispute.closed |
A dispute was closed |
recurring-payment.started |
A subscription began |
recurring-payment.renewed |
A subscription renewed |
recurring-payment.ended |
A subscription ended |
recurring-payment.cancellation.requested |
A subscription cancellation was requested |
recurring-payment.cancellation.aborted |
A pending cancellation was aborted |
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 121 B
- examples/express/package.json 366 B
- examples/express/README.md 1.2 KB
- examples/express/src/index.js 4.3 KB runs code
- examples/express/test/webhook.test.js 4.8 KB runs code
- examples/fastapi/.env.example 121 B
- examples/fastapi/main.py 3.7 KB runs code
- examples/fastapi/README.md 1.5 KB
- examples/fastapi/requirements.txt 82 B
- examples/fastapi/test_webhook.py 4.6 KB runs code
- examples/nextjs/.env.example 121 B
- examples/nextjs/app/webhooks/tebex/route.ts 3.8 KB runs code
- examples/nextjs/package.json 478 B
- examples/nextjs/README.md 1.3 KB
- examples/nextjs/test/webhook.test.ts 3.5 KB runs code
- examples/nextjs/vitest.config.ts 140 B runs code
- references/overview.md 2.5 KB
- references/setup.md 2.4 KB
- references/verification.md 4.7 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 · 143 lines · 55 tokens per session scan A 9a72191aa4a6
tebex-webhooks is a skill published in the GitHub repository hookdeck/webhook-skills (84 stars, last pushed 2d ago), licensed MIT. It adds 55 tokens to every session and 1,577 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to adyen-webhooks, differing in 170 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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
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…