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/workos-webhooksnpx skills add hookdeck/webhook-skills --skill workos-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/workos-webhooks)<a href="https://agentmods.dev/skills/hookdeck/webhook-skills/workos-webhooks"><img src="https://agentmods.dev/badge/skills/hookdeck/webhook-skills/workos-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.00058 | $0.01499 |
| Opus 5 | $0.00029 | $0.00749 |
| Sonnet 5 | $0.00012 | $0.00300 |
| Haiku 4.5 | $0.00006 | $0.00150 |
Grade A, and why
workos-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.
How it starts
The opening of the file, as written. The whole thing — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
WorkOS Webhooks
WorkOS is an enterprise-readiness platform (SSO, Directory Sync, AuthKit). It delivers webhooks for Directory Sync, SSO connection, and User Management events so your app can react to changes in enterprise identity providers.
When to Use This Skill
- How do I receive WorkOS webhooks?
- How do I verify the WorkOS-Signature header?
- Why is my WorkOS webhook signature verification failing?
- How do I handle dsync.user.created or dsync.group.user_added events?
- How do I react to connection.activated, user.created, or session.created?
Verification (core)
WorkOS signs each webhook with the WorkOS-Signature header, formatted
t=<timestamp>, v1=<signature>. The signature is an HMAC-SHA256 hex digest
over `${timestamp}.${rawBody}` using the endpoint signing secret. The
timestamp is in milliseconds; reject anything older than the tolerance
(default 180000 ms / 3 min) to prevent replay. Always use the raw request
body — don't JSON.parse first (the Node SDK re-JSON.stringifys objects,
which can change the bytes and break verification).
Node (official @workos-inc/node SDK — parses + verifies in one call):
const { WorkOS } = require('@workos-inc/node');
const workos = new WorkOS(process.env.WORKOS_API_KEY);
const event = await workos.webhooks.constructEvent({
payload: rawBody, // string/Buffer of the raw HTTP body
sigHeader: req.headers['workos-signature'],
secret: process.env.WORKOS_WEBHOOK_SECRET, // endpoint signing secret
});
// Throws SignatureVerificationException on tampering or a stale timestamp.
// event.event is the type string (e.g. 'dsync.user.created'); event.data is the object.
Manual (any language — for frameworks the SDK doesn't cover, e.g. FastAPI):
ts, sig = parse_workos_signature(header) # "t=..., v1=..."
if int(time.time() * 1000) - int(ts) > 180_000: # milliseconds!
reject()
expected = hmac.new(secret.encode(), f"{ts}.{raw_body}".encode(), hashlib.sha256).hexdigest()
hmac.compare_digest(expected, sig) # timing-safe
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 292 B
- examples/express/package.json 403 B
- examples/express/README.md 1.4 KB
- examples/express/src/index.js 2.9 KB runs code
- examples/express/test/webhook.test.js 5.4 KB runs code
- examples/fastapi/.env.example 137 B
- examples/fastapi/main.py 3.4 KB runs code
- examples/fastapi/README.md 1.8 KB
- examples/fastapi/requirements.txt 82 B
- examples/fastapi/test_webhook.py 4.9 KB runs code
- examples/nextjs/.env.example 252 B
- examples/nextjs/app/webhooks/workos/route.ts 2.3 KB runs code
- examples/nextjs/package.json 514 B
- examples/nextjs/README.md 1.4 KB
- examples/nextjs/test/webhook.test.ts 4.4 KB runs code
- examples/nextjs/vitest.config.ts 398 B runs code
- references/overview.md 2.9 KB
- references/setup.md 2.3 KB
- references/verification.md 4.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.
- yesterday First seen · 129 lines · 58 tokens per session scan A a68fb1e8f0bf
workos-webhooks is a skill published in the GitHub repository hookdeck/webhook-skills (84 stars, last pushed yesterday), licensed MIT. It adds 58 tokens to every session and 1,499 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.
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…