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/recharge-webhooksnpx skills add hookdeck/webhook-skills --skill recharge-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/recharge-webhooks)<a href="https://agentmods.dev/skills/hookdeck/webhook-skills/recharge-webhooks"><img src="https://agentmods.dev/badge/skills/hookdeck/webhook-skills/recharge-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.00073 | $0.02668 |
| Opus 5 | $0.00036 | $0.01334 |
| Sonnet 5 | $0.00015 | $0.00534 |
| Haiku 4.5 | $0.00007 | $0.00267 |
Grade A, and why
recharge-webhooks scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl 'https://api.rechargeapps.com/webhooks' \ How it starts
The opening of the file, as written. The whole thing — 240 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Recharge Webhooks
When to Use This Skill
- How do I receive Recharge webhooks?
- How do I verify Recharge webhook signatures?
- Why is my
X-Recharge-Webhook-SignatureorX-Recharge-Hmac-Sha256verification failing? - How do I handle
charge/paid,charge/failed, orsubscription/cancelledevents? - How do I create a Recharge webhook subscription via the API?
Verification (core)
Every webhook delivery includes two signature schemes: a recommended timestamp-bound scheme (use this for all new integrations) and a legacy body-only scheme that remains supported.
Recommended: timestamp-bound scheme
Two headers are sent:
X-Recharge-Webhook-Timestamp— Unix epoch seconds (integer) at the time the request was signed.X-Recharge-Webhook-Signature— comma-separated key/value pairs in the formt=<epoch>,v1=<hex>(future schemes may addv2=…, so parse by key).
To verify:
- Parse
tandv1fromX-Recharge-Webhook-Signature(tmatches the timestamp header). - Reject if
abs(now - t) > 172800seconds (48 hours) — replay protection. - Compute HMAC-SHA-256, keyed by the API Client Secret, over
"<timestamp>.<payload_json>"— the timestamp, a literal dot, then the exact raw JSON bytes as transmitted (re-serializing breaks it). - Compare the hex digest to
v1with a constant-time comparison.
Node:
const crypto = require('crypto');
function verifyRechargeWebhookTimestamped(rawBody, signatureHeader, clientSecret) {
if (!signatureHeader) return false;
// Parse `t=<epoch>,v1=<hex>` by key.
const parts = Object.fromEntries(
signatureHeader.split(',').map((pair) => pair.split('=').map((s) => s.trim()))
);
const timestamp = parseInt(parts.t, 10);
if (!Number.isFinite(timestamp) || !parts.v1) return false;
// Reject deliveries outside the 48-hour window.
if (Math.abs(Math.floor(Date.now() / 1000) - timestamp) > 172800) return false;
// HMAC-SHA-256 over "<timestamp>.<raw body>", keyed by the client secret.
const digest = crypto
.createHmac('sha256', clientSecret)
.update(`${timestamp}.`)
.update(rawBody)
.digest('hex');
try {
return crypto.timingSafeEqual(Buffer.from(digest), Buffer.from(parts.v1));
} catch {
return false; // length mismatch = invalid
}
}
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 213 B
- examples/express/package.json 372 B
- examples/express/README.md 1.8 KB
- examples/express/src/index.js 6.2 KB runs code
- examples/express/test/webhook.test.js 10 KB runs code
- examples/fastapi/.env.example 213 B
- examples/fastapi/main.py 5.4 KB runs code
- examples/fastapi/README.md 2.0 KB
- examples/fastapi/requirements.txt 82 B
- examples/fastapi/test_webhook.py 11 KB runs code
- examples/nextjs/.env.example 213 B
- examples/nextjs/app/webhooks/recharge/route.ts 5.1 KB runs code
- examples/nextjs/package.json 484 B
- examples/nextjs/README.md 1.9 KB
- examples/nextjs/test/webhook.test.ts 8.6 KB runs code
- examples/nextjs/vitest.config.ts 140 B runs code
- references/overview.md 4.6 KB
- references/setup.md 3.4 KB
- references/verification.md 10 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 · 240 lines · 73 tokens per session scan A 9d8534d1b8c6
recharge-webhooks is a skill published in the GitHub repository hookdeck/webhook-skills (84 stars, last pushed yesterday), licensed MIT. It adds 73 tokens to every session and 2,668 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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…
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…