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/clerk-webhooksnpx skills add hookdeck/webhook-skills --skill clerk-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/clerk-webhooks)<a href="https://agentmods.dev/skills/hookdeck/webhook-skills/clerk-webhooks"><img src="https://agentmods.dev/badge/skills/hookdeck/webhook-skills/clerk-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.00042 | $0.02136 |
| Opus 5 | $0.00021 | $0.01068 |
| Sonnet 5 | $0.00008 | $0.00427 |
| Haiku 4.5 | $0.00004 | $0.00214 |
Grade A, and why
clerk-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 4d 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
84% identical to adyen-webhooks — 230 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 — 201 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Clerk Webhooks
When to Use This Skill
- Setting up Clerk webhook handlers
- Debugging signature verification failures
- Understanding Clerk event types and payloads
- Handling user, session, or organization events
Essential Code (USE THIS)
Express Webhook Handler
Clerk uses the Standard Webhooks protocol (Clerk sends svix-* headers; same format). Use the standardwebhooks npm package:
const express = require('express');
const { Webhook } = require('standardwebhooks');
const app = express();
// CRITICAL: Use express.raw() for webhook endpoint - verification needs raw body
app.post('/webhooks/clerk',
express.raw({ type: 'application/json' }),
async (req, res) => {
const secret = process.env.CLERK_WEBHOOK_SECRET || process.env.CLERK_WEBHOOK_SIGNING_SECRET;
if (!secret || !secret.startsWith('whsec_')) {
return res.status(500).json({ error: 'Server configuration error' });
}
const svixId = req.headers['svix-id'];
const svixTimestamp = req.headers['svix-timestamp'];
const svixSignature = req.headers['svix-signature'];
if (!svixId || !svixTimestamp || !svixSignature) {
return res.status(400).json({ error: 'Missing required webhook headers' });
}
// standardwebhooks expects webhook-* header names; Clerk sends svix-* (same protocol)
const headers = {
'webhook-id': svixId,
'webhook-timestamp': svixTimestamp,
'webhook-signature': svixSignature
};
try {
const wh = new Webhook(secret);
const event = wh.verify(req.body, headers);
if (!event) return res.status(400).json({ error: 'Invalid payload' });
switch (event.type) {
case 'user.created': console.log('User created:', event.data.id); break;
case 'user.updated': console.log('User updated:', event.data.id); break;
case 'session.created': console.log('Session created:', event.data.user_id); break;
case 'organization.created': console.log('Organization created:', event.data.id); break;
default: console.log('Unhandled:', event.type);
}
res.status(200).json({ success: true });
} catch (err) {
res.status(400).json({ error: err.name === 'WebhookVerificationError' ? err.message : 'Webhook verification failed' });
}
}
);
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 146 B
- examples/express/package.json 492 B
- examples/express/README.md 1.1 KB
- examples/express/src/index.js 3.6 KB runs code
- examples/express/test/webhook.test.js 6.8 KB runs code
- examples/fastapi/.env.example 146 B
- examples/fastapi/main.py 4.9 KB runs code
- examples/fastapi/README.md 1.3 KB
- examples/fastapi/requirements.txt 114 B
- examples/fastapi/test_webhook.py 6.9 KB runs code
- examples/nextjs/.env.example 146 B
- examples/nextjs/app/webhooks/clerk/route.ts 2.4 KB runs code
- examples/nextjs/package.json 609 B
- examples/nextjs/README.md 1.3 KB
- examples/nextjs/test/webhook.test.ts 7.6 KB runs code
- examples/nextjs/vitest.config.ts 161 B runs code
- references/overview.md 3.2 KB
- references/patterns.md 3.5 KB
- references/setup.md 3.4 KB
- references/verification.md 7.8 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.
- 4d ago First seen · 201 lines · 42 tokens per session scan A 9c7acf459d43
clerk-webhooks is a skill published in the GitHub repository hookdeck/webhook-skills (84 stars, last pushed today), licensed MIT. It adds 42 tokens to every session and 2,136 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 84% identical to adyen-webhooks, differing in 230 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…