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 mailgun-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/mailgun-webhooks)<a href="https://agentmods.dev/skills/hookdeck/webhook-skills/mailgun-webhooks"><img src="https://agentmods.dev/badge/skills/hookdeck/webhook-skills/mailgun-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/mailgun-webhooks"><img src="https://agentmods.dev/badge/skills/hookdeck/webhook-skills/mailgun-webhooks.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 206 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00047 | $0.02492 |
| Opus 5.5 | $0.00019 | $0.00997 |
| Sonnet 5.5 | $0.00009 | $0.00498 |
| Haiku 4.5 | $0.00005 | $0.00249 |
Grade A, and why
mailgun-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 1mo 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 — 243 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mailgun Webhooks
When to Use This Skill
- Setting up Mailgun webhook handlers
- Verifying Mailgun webhook signatures (HMAC-SHA256 over
timestamp + token) - Debugging Mailgun signature verification failures
- Handling email delivery events:
delivered,failed,opened,clicked - Handling list events:
unsubscribed,complained - Distinguishing permanent vs temporary failures via the
severityfield - Verifying subaccount webhooks via the optional
parent-signaturefield
How Mailgun Webhooks Differ
Unlike most providers, Mailgun puts the signature inside the request body, not in a header. The webhook payload always has this shape:
{
"signature": {
"timestamp": "1529006854",
"token": "a8ce0edb2dd8301dee6c2405235584e45aa91d1e9f979f3de0",
"signature": "d2271d12299f6592d9d44cd9d250f0704e4674c30d79d07c47a66f95ce71cf55"
},
"event-data": { "event": "delivered", "...": "..." }
}
Verify by computing HMAC-SHA256(signing_key, timestamp + token) and comparing the hex digest to signature.signature using timing-safe equality.
Essential Code (USE THIS)
Node.js — Verify Signature
const crypto = require('crypto');
function verifyMailgun(signature, signingKey) {
// signature is the `signature` object from the request body
const { timestamp, token, signature: providedSig } = signature;
if (!timestamp || !token || !providedSig) return false;
const expected = crypto
.createHmac('sha256', signingKey)
.update(timestamp + token) // concatenate, no separator
.digest('hex');
// Timing-safe comparison
try {
return crypto.timingSafeEqual(
Buffer.from(expected, 'hex'),
Buffer.from(providedSig, 'hex')
);
} catch {
return false; // length mismatch
}
}
Express Webhook Handler
const express = require('express');
const crypto = require('crypto');
const app = express();
app.post('/webhooks/mailgun', express.json(), (req, res) => {
const { signature, 'event-data': eventData } = req.body;
if (!signature || !verifyMailgun(signature, process.env.MAILGUN_WEBHOOK_SIGNING_KEY)) {
return res.status(400).json({ error: 'Invalid signature' });
}
switch (eventData.event) {
case 'delivered':
console.log('Delivered:', eventData.recipient);
break;
case 'failed':
// severity: 'permanent' (hard bounce) or 'temporary' (soft bounce)
console.log(`Failed (${eventData.severity}):`, eventData.recipient);
break;
case 'opened':
console.log('Opened:', eventData.recipient);
break;
case 'clicked':
console.log('Clicked:', eventData.url);
break;
case 'unsubscribed':
case 'complained':
console.log(`${eventData.event}:`, eventData.recipient);
break;
}
res.json({ received: true });
});
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 357 B
- examples/express/package.json 480 B
- examples/express/README.md 1.8 KB
- examples/express/src/index.js 4.6 KB runs code
- examples/express/test/webhook.test.js 7.2 KB runs code
- examples/fastapi/.env.example 299 B
- examples/fastapi/main.py 4.6 KB runs code
- examples/fastapi/README.md 1.5 KB
- examples/fastapi/requirements.txt 115 B
- examples/fastapi/test_webhook.py 6.1 KB runs code
- examples/nextjs/.env.example 260 B
- examples/nextjs/app/webhooks/mailgun/route.ts 4.6 KB runs code
- examples/nextjs/package.json 613 B
- examples/nextjs/README.md 1.4 KB
- examples/nextjs/test/webhook.test.ts 6.2 KB runs code
- examples/nextjs/vitest.config.ts 283 B runs code
- references/overview.md 4.4 KB
- references/setup.md 4.8 KB
- references/verification.md 7.4 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.
- 1mo ago First seen · 243 lines · 47 tokens per session scan A 0562eb9e696f
mailgun-webhooks is a skill published in the GitHub repository hookdeck/webhook-skills (95 stars, last pushed today), licensed MIT. It adds 47 tokens to every session and 2,492 once invoked, about $0.0002 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-09-03.
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…