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/openai-webhooksnpx skills add hookdeck/webhook-skills --skill openai-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/openai-webhooks)<a href="https://agentmods.dev/skills/hookdeck/webhook-skills/openai-webhooks"><img src="https://agentmods.dev/badge/skills/hookdeck/webhook-skills/openai-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.00050 | $0.02375 |
| Opus 5 | $0.00025 | $0.01188 |
| Sonnet 5 | $0.00010 | $0.00475 |
| Haiku 4.5 | $0.00005 | $0.00237 |
Grade A, and why
openai-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 today.
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 — 276 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OpenAI Webhooks
When to Use This Skill
- Setting up OpenAI webhook handlers for async operations
- Debugging signature verification failures
- Handling fine-tuning job completion events
- Processing batch API completion notifications
- Handling realtime API incoming calls
Essential Code (USE THIS)
Express Webhook Handler
const express = require('express');
const crypto = require('crypto');
const app = express();
// Standard Webhooks signature verification for OpenAI
function verifyOpenAISignature(payload, webhookId, webhookTimestamp, webhookSignature, secret) {
if (!webhookSignature || !webhookSignature.includes(',')) {
return false;
}
// Check timestamp is within 5 minutes to prevent replay attacks
const currentTime = Math.floor(Date.now() / 1000);
const timestampDiff = currentTime - parseInt(webhookTimestamp);
if (timestampDiff > 300 || timestampDiff < -300) {
console.error('Webhook timestamp too old or too far in the future');
return false;
}
// Extract version and signature
const [version, signature] = webhookSignature.split(',');
if (version !== 'v1') {
return false;
}
// Create signed content: webhook_id.webhook_timestamp.payload
const payloadStr = payload instanceof Buffer ? payload.toString('utf8') : payload;
const signedContent = `${webhookId}.${webhookTimestamp}.${payloadStr}`;
// Decode base64 secret (remove whsec_ prefix if present)
const secretKey = secret.startsWith('whsec_') ? secret.slice(6) : secret;
const secretBytes = Buffer.from(secretKey, 'base64');
// Generate expected signature
const expectedSignature = crypto
.createHmac('sha256', secretBytes)
.update(signedContent, 'utf8')
.digest('base64');
// Timing-safe comparison
return crypto.timingSafeEqual(
Buffer.from(signature),
Buffer.from(expectedSignature)
);
}
// CRITICAL: Use express.raw() for webhook endpoint - OpenAI needs raw body
app.post('/webhooks/openai',
express.raw({ type: 'application/json' }),
async (req, res) => {
const webhookId = req.headers['webhook-id'];
const webhookTimestamp = req.headers['webhook-timestamp'];
const webhookSignature = req.headers['webhook-signature'];
// Verify signature
if (!verifyOpenAISignature(
req.body,
webhookId,
webhookTimestamp,
webhookSignature,
process.env.OPENAI_WEBHOOK_SECRET
)) {
console.error('Invalid OpenAI webhook signature');
return res.status(400).send('Invalid signature');
}
// Parse the verified payload
const event = JSON.parse(req.body.toString());
// Handle the event
switch (event.type) {
case 'fine_tuning.job.succeeded':
console.log('Fine-tuning job succeeded:', event.data.id);
break;
case 'fine_tuning.job.failed':
console.log('Fine-tuning job failed:', event.data.id);
break;
case 'batch.completed':
console.log('Batch completed:', event.data.id);
break;
case 'batch.failed':
console.log('Batch failed:', event.data.id);
break;
case 'batch.cancelled':
console.log('Batch cancelled:', event.data.id);
break;
case 'batch.expired':
console.log('Batch expired:', event.data.id);
break;
case 'realtime.call.incoming':
console.log('Realtime call incoming:', event.data.id);
break;
default:
console.log('Unhandled event:', event.type);
}
res.json({ received: true });
}
);
What ships with it
22 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 426 B
- examples/express/package.json 480 B
- examples/express/README.md 1.2 KB
- examples/express/src/index.js 5.2 KB runs code
- examples/express/test/webhook.test.js 9.0 KB runs code
- examples/fastapi/.env.example 426 B
- examples/fastapi/main.py 5.6 KB runs code
- examples/fastapi/README.md 1.5 KB
- examples/fastapi/requirements.txt 121 B
- examples/fastapi/test_webhook.py 10 KB runs code
- examples/nextjs/.env.example 392 B
- examples/nextjs/app/webhooks/openai/route.ts 4.6 KB runs code
- examples/nextjs/package.json 651 B
- examples/nextjs/README.md 1.2 KB
- examples/nextjs/test/setup.ts 155 B runs code
- examples/nextjs/test/webhook.test.ts 10 KB runs code
- examples/nextjs/tsconfig.json 573 B
- examples/nextjs/vitest.config.ts 345 B runs code
- references/overview.md 2.6 KB
- references/setup.md 3.0 KB
- references/verification.md 9.0 KB
- TODO.md 394 B
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.
- today First seen · 276 lines · 50 tokens per session scan A d1cead7f950e
openai-webhooks is a skill published in the GitHub repository hookdeck/webhook-skills (84 stars, last pushed today), licensed MIT. It adds 50 tokens to every session and 2,375 once invoked, about $0.0003 per session on Opus 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
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…