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/auth0-webhooksnpx skills add hookdeck/webhook-skills --skill auth0-webhooksgit clone --depth 1 https://github.com/hookdeck/webhook-skillsWhat 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.00069 | $0.01390 |
| Opus 5 | $0.00034 | $0.00695 |
| Sonnet 5 | $0.00014 | $0.00278 |
| Haiku 4.5 | $0.00007 | $0.00139 |
Grade A, and why
auth0-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.
How it starts
The opening of the file, as written. The whole thing — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Auth0 Webhooks
Auth0 (by Okta) does not send classic per-event webhooks. Instead you create a Custom Log Stream (HTTP) that batches tenant log events and POSTs them to your endpoint as a JSON array of log records.
When to Use This Skill
- How do I receive Auth0 webhooks / Custom Log Stream events?
- How do I secure an Auth0 log stream HTTP endpoint?
- How do I validate the Auth0 Authorization token on incoming requests?
- How do I handle batched arrays of Auth0 log events?
- Why does Auth0 keep retrying my log stream endpoint?
Verification (core)
Auth0 log streams have no HMAC signature. You secure the endpoint with a
static shared secret: configure an Authorization header value on the log
stream, then compare it against the incoming Authorization header on every
request using a timing-safe comparison. Always serve the endpoint over
HTTPS.
const crypto = require('crypto');
// Compare the incoming Authorization header against the configured token.
function verifyAuth0Token(headerValue, expectedToken) {
if (!headerValue || !expectedToken) return false;
const a = Buffer.from(headerValue);
const b = Buffer.from(expectedToken);
if (a.length !== b.length) return false; // timingSafeEqual requires equal length
return crypto.timingSafeEqual(a, b);
}
Then process the payload — a JSON array of log records — and return 2xx
quickly. Auth0 retries on any non-2xx response, so acknowledge first and do
slow work asynchronously.
For complete handlers with route wiring, batch iteration, event dispatch, and tests, see:
Common Event Types
Each record's type is in event.data.type (a short log event type code):
| Code | Description |
|---|---|
s |
Success Login |
f |
Failed Login |
ss |
Success Signup |
fs |
Failed Signup |
sepft |
Success Exchange (Password for Access Token) |
seacft |
Success Exchange (Authorization Code for Access Token) |
feacft |
Failed Exchange (Authorization Code for Access Token) |
slo |
Success Logout |
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 305 B
- examples/express/package.json 384 B
- examples/express/README.md 1.5 KB
- examples/express/src/index.js 3.3 KB runs code
- examples/express/test/webhook.test.js 3.1 KB runs code
- examples/fastapi/.env.example 236 B
- examples/fastapi/main.py 2.8 KB runs code
- examples/fastapi/README.md 1.5 KB
- examples/fastapi/requirements.txt 82 B
- examples/fastapi/test_webhook.py 2.8 KB runs code
- examples/nextjs/.env.example 236 B
- examples/nextjs/app/webhooks/auth0/route.ts 3.0 KB runs code
- examples/nextjs/package.json 495 B
- examples/nextjs/README.md 1.4 KB
- examples/nextjs/test/webhook.test.ts 2.8 KB runs code
- examples/nextjs/vitest.config.ts 140 B runs code
- references/overview.md 3.3 KB
- references/setup.md 2.8 KB
- references/verification.md 3.3 KB
- TODO.md 2.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 · 124 lines · 69 tokens per session scan A 0dbc90aa6270
auth0-webhooks is a skill published in the GitHub repository hookdeck/webhook-skills (84 stars, last pushed 6d ago), licensed MIT. It adds 69 tokens to every session and 1,390 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-08-30.
Other skills, from other repositories
wiki
Rebuild a flow-first project wiki using the mimirs wiki MCP tool. Use when the user asks to generate, rebuild, refresh, or write the wiki for a codebase.
scout
Research the web for solutions, competitors, alternatives, or prior art for a decision facing this project — then store the findings in project memory so they survive the session. Use when choosing a library or approach, comparing tools, checking what others do, or evaluating whether to build vs adopt.
plan
Design an implementation plan before writing code — where the change lands, what it will touch, what could break, and the steps in order. Use when asked to plan a feature, scope a change, or figure out how to approach an edit before making it. To assess a change that already exists (a diff, refactor, or rename), use…
research
Answer a hard, open-ended question about how the project works or is built by synthesizing every source — code, structure, git history, prior decisions, discussion, caveats — and verifying each claim against the source. Use for deep cross-cutting questions that span more than one area. Narrower siblings — a single…
explore
Build an accurate mental model of an unfamiliar codebase, feature, or area before changing it — where it lives, how it connects, what it does, and why. Use when asked how something works, where something is, when onboarding to a repo, or before editing code you don't know. For a cross-cutting question that needs…
handoff
Wrap up a work session so the next session (or another agent) can pick up cleanly — what was done, what's in flight, what to watch out for. Use when ending a session, switching tasks, or asked to hand off, wrap up, or save state for later.