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 skills add hookdeck/webhook-skills --skill auth0-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/auth0-webhooks)<a href="https://agentmods.dev/skills/hookdeck/webhook-skills/auth0-webhooks"><img src="https://agentmods.dev/badge/skills/hookdeck/webhook-skills/auth0-webhooks/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/hookdeck/webhook-skills/auth0-webhooks"><img src="https://agentmods.dev/badge/skills/hookdeck/webhook-skills/auth0-webhooks.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 4 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 70 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 71 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 72 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- medium MCP Rug Pull · line 88 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.1 | $0.00070 | $0.01418 |
| Opus 5.5 | $0.00028 | $0.00567 |
| Sonnet 5.5 | $0.00014 | $0.00284 |
| Haiku 4.5 | $0.00007 | $0.00142 |
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 8d 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 — 125 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 POSTs tenant log events to your endpoint. Set the stream's Content Format to JSON Array and each request body is a JSON array of log records, which is what the examples here parse.
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 with the JSON Array
content format) 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.6 KB
- references/setup.md 3.1 KB
- references/verification.md 3.4 KB
- TODO.md 883 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.
- 8d ago Changed · +1 lines · +1 tokens per session e25bad61b8b2
- 1mo 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 (92 stars, last pushed yesterday), licensed MIT. It adds 70 tokens to every session and 1,418 once invoked, about $0.0003 per session on Opus 5.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
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…