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/neon-webhooksnpx skills add hookdeck/webhook-skills --skill neon-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/neon-webhooks)<a href="https://agentmods.dev/skills/hookdeck/webhook-skills/neon-webhooks"><img src="https://agentmods.dev/badge/skills/hookdeck/webhook-skills/neon-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.00059 | $0.01952 |
| Opus 5 | $0.00030 | $0.00976 |
| Sonnet 5 | $0.00012 | $0.00390 |
| Haiku 4.5 | $0.00006 | $0.00195 |
Grade A, and why
neon-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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
const jwks = await fetch(jwksUrl).then((r) => r.json()); // cache these keys by kid How it starts
The opening of the file, as written. The whole thing — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Neon Webhooks
When to Use This Skill
- Setting up Neon Auth webhook handlers
- How do I verify Neon webhook signatures?
- Why is my Neon webhook signature verification failing?
- Understanding Neon Auth event types and blocking vs non-blocking events
- Handling
user.created,user.before_create,send.otp,send.magic_link, orphone_number.verified
Verification (core)
Neon Auth signs each webhook with EdDSA (Ed25519) as a detached JWS — there is no shared secret. You verify with the public key published at <NEON_AUTH_URL>/.well-known/jwks.json, selected by the X-Neon-Signature-Kid header. Do not use svix or an HMAC template — neither applies here.
The critical gotcha is the double base64url encoding of the signing input. A naive `${timestamp}.${body}` reconstruction will always fail. Use the raw request body bytes and note X-Neon-Timestamp is in milliseconds.
import crypto from 'node:crypto';
// X-Neon-Signature is a detached JWS: "header..signature" (empty middle section).
async function verifyNeonWebhook(rawBody, headers, jwksUrl) {
const [headerB64, emptyPayload, signatureB64] = headers['x-neon-signature'].split('.');
if (emptyPayload !== '') throw new Error('Expected detached JWS (header..signature)');
const jwks = await fetch(jwksUrl).then((r) => r.json()); // cache these keys by kid
const jwk = jwks.keys.find((k) => k.kid === headers['x-neon-signature-kid']);
if (!jwk) throw new Error('Signing key not found in JWKS');
const publicKey = crypto.createPublicKey({ key: jwk, format: 'jwk' });
// Double base64url: signingInput = header + "." + b64url(timestamp + "." + b64url(rawBody))
const payloadB64 = Buffer.from(rawBody, 'utf8').toString('base64url');
const inner = `${headers['x-neon-timestamp']}.${payloadB64}`; // timestamp is in MILLISECONDS
const signingInput = `${headerB64}.${Buffer.from(inner, 'utf8').toString('base64url')}`;
const ok = crypto.verify(null, Buffer.from(signingInput), publicKey,
Buffer.from(signatureB64, 'base64url')); // null alg = Ed25519
if (!ok) throw new Error('Invalid signature');
return JSON.parse(rawBody); // parse only AFTER verifying
}
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 286 B
- examples/express/package.json 369 B
- examples/express/README.md 1.7 KB
- examples/express/src/index.js 4.8 KB runs code
- examples/express/test/webhook.test.js 4.6 KB runs code
- examples/fastapi/.env.example 222 B
- examples/fastapi/main.py 4.7 KB runs code
- examples/fastapi/README.md 1.8 KB
- examples/fastapi/requirements.txt 103 B
- examples/fastapi/test_webhook.py 5.1 KB runs code
- examples/nextjs/.env.example 222 B
- examples/nextjs/app/webhooks/neon/route.ts 4.5 KB runs code
- examples/nextjs/package.json 481 B
- examples/nextjs/README.md 1.7 KB
- examples/nextjs/test/webhook.test.ts 4.2 KB runs code
- examples/nextjs/tsconfig.json 562 B
- examples/nextjs/vitest.config.ts 140 B runs code
- references/overview.md 2.9 KB
- references/setup.md 2.3 KB
- references/verification.md 6.9 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 · 138 lines · 59 tokens per session scan A b41499188add
neon-webhooks is a skill published in the GitHub repository hookdeck/webhook-skills (84 stars, last pushed yesterday), licensed MIT. It adds 59 tokens to every session and 1,952 once invoked, about $0.0003 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…
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…