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/oura-webhooksnpx skills add hookdeck/webhook-skills --skill oura-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/oura-webhooks)<a href="https://agentmods.dev/skills/hookdeck/webhook-skills/oura-webhooks"><img src="https://agentmods.dev/badge/skills/hookdeck/webhook-skills/oura-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.00053 | $0.01793 |
| Opus 5 | $0.00026 | $0.00897 |
| Sonnet 5 | $0.00011 | $0.00359 |
| Haiku 4.5 | $0.00005 | $0.00179 |
Grade A, and why
oura-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 — 185 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 — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Oura Webhooks
When to Use This Skill
- How do I receive Oura webhooks?
- How do I complete the Oura subscription verification handshake (GET challenge)?
- How do I verify the
x-oura-signatureheader? - Why is my Oura webhook signature verification failing?
- How do I handle Oura
sleep,daily_readiness, orworkoutevents?
How Oura Webhooks Work
Oura webhooks have two distinct request types on the same callback URL:
- Subscription handshake (GET): When you create a subscription, Oura sends a
GETto yourcallback_urlwith query paramsverification_tokenandchallenge. Check the token matches yours, then respond200with JSON{"challenge": "<value>"}. - Event delivery (POST): Each event is a
POSTcarrying headersx-oura-signatureandx-oura-timestamp. Verify the HMAC, then process.
Event payloads are thin — { event_type, data_type, object_id, event_time, user_id }.
Use object_id to fetch the full record from the Oura API.
Verification (core)
HMAC-SHA256 over timestamp + rawBody, keyed with your client secret, hex digest,
UPPERCASE. Compare (timing-safe) to the x-oura-signature header. Use the raw
request body — see references/verification.md for why raw
body is used instead of re-serializing (JSON.stringify) the parsed payload.
Node:
const crypto = require('crypto');
function verifyOuraSignature(rawBody, signature, timestamp, clientSecret) {
if (!signature || !timestamp) return false;
const expected = crypto
.createHmac('sha256', clientSecret)
.update(timestamp + rawBody) // x-oura-timestamp + raw request body
.digest('hex')
.toUpperCase(); // Oura sends an uppercase hex digest
try {
return crypto.timingSafeEqual(Buffer.from(signature), Buffer.from(expected));
} catch {
return false; // length mismatch = invalid
}
}
Python:
import hmac, hashlib
def verify_oura_signature(raw_body: bytes, signature: str, timestamp: str, client_secret: str) -> bool:
if not signature or not timestamp:
return False
expected = hmac.new(
client_secret.encode("utf-8"),
timestamp.encode("utf-8") + raw_body, # x-oura-timestamp + raw request body
hashlib.sha256,
).hexdigest().upper()
return hmac.compare_digest(expected, signature)
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 372 B
- examples/express/package.json 364 B
- examples/express/README.md 1.8 KB
- examples/express/src/index.js 4.1 KB runs code
- examples/express/test/webhook.test.js 5.6 KB runs code
- examples/fastapi/.env.example 372 B
- examples/fastapi/main.py 3.6 KB runs code
- examples/fastapi/README.md 1.4 KB
- examples/fastapi/requirements.txt 82 B
- examples/fastapi/test_webhook.py 5.1 KB runs code
- examples/nextjs/.env.example 372 B
- examples/nextjs/app/webhooks/oura/route.ts 3.4 KB runs code
- examples/nextjs/package.json 476 B
- examples/nextjs/README.md 1.3 KB
- examples/nextjs/test/webhook.test.ts 5.3 KB runs code
- examples/nextjs/vitest.config.ts 140 B runs code
- references/overview.md 3.5 KB
- references/setup.md 3.8 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.
- 2d ago First seen · 160 lines · 53 tokens per session scan A 0a23e8df4589
oura-webhooks is a skill published in the GitHub repository hookdeck/webhook-skills (84 stars, last pushed yesterday), licensed MIT. It adds 53 tokens to every session and 1,793 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 185 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…