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/uber-webhooksnpx skills add hookdeck/webhook-skills --skill uber-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/uber-webhooks)<a href="https://agentmods.dev/skills/hookdeck/webhook-skills/uber-webhooks"><img src="https://agentmods.dev/badge/skills/hookdeck/webhook-skills/uber-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.01605 |
| Opus 5 | $0.00025 | $0.00803 |
| Sonnet 5 | $0.00010 | $0.00321 |
| Haiku 4.5 | $0.00005 | $0.00161 |
Grade A, and why
uber-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
86% identical to adyen-webhooks — 182 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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Uber Webhooks
When to Use This Skill
- How do I receive Uber Eats webhooks?
- How do I verify Uber webhook signatures?
- Why is my
X-Uber-Signatureverification failing? - How do I handle
orders.notificationororders.cancelevents? - Setting up an Uber Eats webhook receiver in Express, Next.js, or FastAPI
Verification (core)
Uber Eats signs the raw request body with HMAC-SHA256 keyed on your app's
client secret and sends the digest as a lowercased hex string in the
X-Uber-Signature header (no sha256= prefix). Pass the raw body bytes,
compute the digest, and compare timing-safe.
Node:
const crypto = require('crypto');
function verifyUberWebhook(rawBody, signatureHeader, clientSecret) {
if (!signatureHeader) return false;
const expected = crypto
.createHmac('sha256', clientSecret)
.update(rawBody)
.digest('hex');
try {
return crypto.timingSafeEqual(
Buffer.from(signatureHeader, 'hex'),
Buffer.from(expected, 'hex')
);
} catch {
return false;
}
}
Python:
import hmac, hashlib
def verify_uber_webhook(raw_body: bytes, signature_header: str, client_secret: str) -> bool:
if not signature_header:
return False
expected = hmac.new(client_secret.encode(), raw_body, hashlib.sha256).hexdigest()
return hmac.compare_digest(signature_header, expected)
For complete handlers with route wiring, event dispatch, and tests, see:
Common Event Types
The event type is in the JSON body's event_type field (not a header).
| Event | Description |
|---|---|
orders.notification |
New order created |
orders.cancel |
Order cancelled (non-v1.0.0 stores) |
orders.failure |
Order cancelled (API v1.0.0 only) |
orders.release |
Fast order release: courier reached the geo-fence |
orders.scheduled.notification |
Scheduled order created (API v1.0.0 only) |
order.fulfillment_issues.resolved |
Customer confirmed a fulfillment change |
store.provisioned |
Store granted app access |
store.deprovisioned |
Store access removed |
store.status.changed |
Store online status changed |
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 180 B
- examples/express/package.json 369 B
- examples/express/README.md 1.0 KB
- examples/express/src/index.js 4.2 KB runs code
- examples/express/test/webhook.test.js 4.7 KB runs code
- examples/fastapi/.env.example 180 B
- examples/fastapi/main.py 3.5 KB runs code
- examples/fastapi/README.md 1.0 KB
- examples/fastapi/requirements.txt 82 B
- examples/fastapi/test_webhook.py 4.7 KB runs code
- examples/nextjs/.env.example 180 B
- examples/nextjs/app/webhooks/uber/route.ts 3.4 KB runs code
- examples/nextjs/package.json 481 B
- examples/nextjs/README.md 878 B
- examples/nextjs/test/webhook.test.ts 3.4 KB runs code
- examples/nextjs/vitest.config.ts 140 B runs code
- references/overview.md 3.1 KB
- references/setup.md 2.6 KB
- references/verification.md 5.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 · 153 lines · 50 tokens per session scan A 55e26e3c1219
uber-webhooks is a skill published in the GitHub repository hookdeck/webhook-skills (84 stars, last pushed yesterday), licensed MIT. It adds 50 tokens to every session and 1,605 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to adyen-webhooks, differing in 182 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…