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/okta-webhooksnpx skills add hookdeck/webhook-skills --skill okta-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/okta-webhooks)<a href="https://agentmods.dev/skills/hookdeck/webhook-skills/okta-webhooks"><img src="https://agentmods.dev/badge/skills/hookdeck/webhook-skills/okta-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.00063 | $0.01650 |
| Opus 5 | $0.00032 | $0.00825 |
| Sonnet 5 | $0.00013 | $0.00330 |
| Haiku 4.5 | $0.00006 | $0.00165 |
Grade A, and why
okta-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 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.
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
81% identical to adyen-webhooks — 187 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 — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Okta Webhooks
When to Use This Skill
- Setting up Okta Event Hook handlers
- Implementing the one-time verification challenge (GET handshake)
- Authenticating Okta webhook requests with the
Authorizationheader secret - Understanding Okta event types and payloads
- Debugging why Okta event hook verification or delivery is failing
How Okta Event Hooks Differ
Okta Event Hooks do not use an HMAC signature. Security relies on two things:
- One-time verification handshake — When you register the hook, Okta sends a
GET request with an
x-okta-verification-challengeheader. You must reply200with JSON{"verification": "<challenge value>"}. - Per-request authentication — You choose a secret string that Okta sends in
the
Authorizationheader on every event delivery (an HTTPS POST). Verify it with a timing-safe comparison. There is no body signature.
Verification (core)
const crypto = require('crypto');
// 1. One-time verification handshake (GET)
function handleChallenge(req, res) {
const challenge = req.headers['x-okta-verification-challenge'];
return res.status(200).json({ verification: challenge });
}
// 2. Per-request auth on every event POST — timing-safe compare of Authorization
function isAuthorized(authHeader, secret) {
const a = Buffer.from(authHeader || '', 'utf8');
const b = Buffer.from(secret || '', 'utf8');
// Length check first: timingSafeEqual throws on unequal-length buffers
return a.length === b.length && crypto.timingSafeEqual(a, b);
}
Python timing-safe compare: hmac.compare_digest(auth_header, secret).
For complete handlers with route wiring, event dispatch, and tests, see:
Common Event Types
Okta event hooks deliver System Log
events. Each item in data.events[] has an eventType field:
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 230 B
- examples/express/package.json 391 B
- examples/express/README.md 1.6 KB
- examples/express/src/index.js 2.9 KB runs code
- examples/express/test/webhook.test.js 2.2 KB runs code
- examples/fastapi/.env.example 190 B
- examples/fastapi/main.py 2.8 KB runs code
- examples/fastapi/README.md 1.7 KB
- examples/fastapi/requirements.txt 102 B
- examples/fastapi/test_webhook.py 2.2 KB runs code
- examples/nextjs/.env.example 188 B
- examples/nextjs/app/webhooks/okta/route.ts 3.0 KB runs code
- examples/nextjs/package.json 511 B
- examples/nextjs/README.md 1.6 KB
- examples/nextjs/test/webhook.test.ts 2.6 KB runs code
- examples/nextjs/vitest.config.ts 157 B runs code
- references/overview.md 3.8 KB
- references/setup.md 3.3 KB
- references/verification.md 4.2 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 · 152 lines · 63 tokens per session scan A 7451c8013164
okta-webhooks is a skill published in the GitHub repository hookdeck/webhook-skills (84 stars, last pushed yesterday), licensed MIT. It adds 63 tokens to every session and 1,650 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 81% identical to adyen-webhooks, differing in 187 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.
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…