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/recurly-webhooksnpx skills add hookdeck/webhook-skills --skill recurly-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/recurly-webhooks)<a href="https://agentmods.dev/skills/hookdeck/webhook-skills/recurly-webhooks"><img src="https://agentmods.dev/badge/skills/hookdeck/webhook-skills/recurly-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.00071 | $0.01942 |
| Opus 5 | $0.00036 | $0.00971 |
| Sonnet 5 | $0.00014 | $0.00388 |
| Haiku 4.5 | $0.00007 | $0.00194 |
Grade A, and why
recurly-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 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.
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
75% identical to adyen-webhooks — 193 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 — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Recurly Webhooks
When to Use This Skill
- How do I receive Recurly webhooks?
- How do I verify the Recurly
recurly-signatureheader? - How do I secure a Recurly webhook endpoint with HTTP Basic Auth?
- How do I handle
new_subscription_notificationorsuccessful_payment_notification? - Why is my Recurly webhook signature verification failing?
How Recurly Secures Webhooks
Recurly webhooks are secured with up to three layers. Use all that apply:
- Signature (JSON payloads only). Recurly signs JSON notifications and sends
the signature in a
recurly-signatureheader. This is the primary integrity check — always verify it. (Legacy XML payloads are not signed.) - HTTP Basic Auth. Configure a username/password on the endpoint in Recurly;
Recurly sends them in the
Authorizationheader on every request. - IP allowlist. Accept requests only from Recurly's published IP ranges.
Prefer the JSON payload format so you get signature verification. The
official Recurly SDK (recurly) is an API client and does not ship a webhook
verification helper, so verify the signature manually with HMAC-SHA256.
Verification (core)
The recurly-signature header is a Unix timestamp (ms) followed by one or more
hex HMAC-SHA256 signatures, comma-separated:
recurly-signature: 1659641851000,a8c8524a0cdd99e3...,cafe677a2e6fa177...
Signed message is `${timestamp}.${rawBody}` (the raw, unparsed body).
Multiple signatures appear during a 24h key rotation; the notification is valid
if any one matches. Use a constant-time compare.
const crypto = require('crypto');
function verifyRecurlySignature(rawBody, header, secret) {
if (!header || !secret) return false;
const [timestamp, ...signatures] = header.split(',');
if (!timestamp || signatures.length === 0) return false;
const expected = crypto
.createHmac('sha256', secret)
.update(`${timestamp}.`)
.update(rawBody) // Buffer/string of the raw request body
.digest('hex');
const expBuf = Buffer.from(expected);
return signatures.some((sig) => {
const sigBuf = Buffer.from(sig.trim());
return sigBuf.length === expBuf.length && crypto.timingSafeEqual(sigBuf, expBuf);
});
}
What ships with it
20 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 465 B
- examples/express/package.json 370 B
- examples/express/README.md 2.1 KB
- examples/express/src/index.js 6.0 KB runs code
- examples/express/test/webhook.test.js 5.0 KB runs code
- examples/fastapi/.env.example 425 B
- examples/fastapi/main.py 5.2 KB runs code
- examples/fastapi/README.md 2.2 KB
- examples/fastapi/requirements.txt 82 B
- examples/fastapi/test_webhook.py 4.8 KB runs code
- examples/nextjs/.env.example 425 B
- examples/nextjs/app/webhooks/recurly/route.ts 3.5 KB runs code
- examples/nextjs/app/webhooks/recurly/verify.ts 2.2 KB runs code
- examples/nextjs/package.json 481 B
- examples/nextjs/README.md 2.2 KB
- examples/nextjs/test/webhook.test.ts 4.0 KB runs code
- examples/nextjs/vitest.config.ts 140 B runs code
- references/overview.md 5.6 KB
- references/setup.md 3.2 KB
- references/verification.md 5.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.
- yesterday First seen · 172 lines · 71 tokens per session scan A a4741cdc5e24
recurly-webhooks is a skill published in the GitHub repository hookdeck/webhook-skills (84 stars, last pushed yesterday), licensed MIT. It adds 71 tokens to every session and 1,942 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 75% identical to adyen-webhooks, differing in 193 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…
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…