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/zerohash-webhooksnpx skills add hookdeck/webhook-skills --skill zerohash-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/zerohash-webhooks)<a href="https://agentmods.dev/skills/hookdeck/webhook-skills/zerohash-webhooks"><img src="https://agentmods.dev/badge/skills/hookdeck/webhook-skills/zerohash-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.00051 | $0.01969 |
| Opus 5 | $0.00026 | $0.00984 |
| Sonnet 5 | $0.00010 | $0.00394 |
| Haiku 4.5 | $0.00005 | $0.00197 |
Grade A, and why
zerohash-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 yesterday.
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 — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Zero Hash Webhooks
When to Use This Skill
- How do I receive Zero Hash webhooks?
- How do I verify Zero Hash webhook signatures (
x-zh-hook-signature)? - How do I handle
trade_status_changedandpayment_status_changedevents? - Why is my Zero Hash webhook signature verification failing?
- How do I guard Zero Hash webhooks against replay attacks with
x-zh-hook-timestamp?
Verification (core)
Zero Hash signs the raw request body with HMAC-SHA256 and sends the digest as a hex string. There is no webhook SDK — verify manually.
The recommended (replay-protected) scheme signs payload + timestamp
(concatenated raw strings, no delimiter) and sends:
x-zh-hook-signature—to_hex(hmac_sha256(payload + timestamp, secret))x-zh-hook-timestamp— the UNIX timestamp that was signed
Reject the request if the timestamp is not within ±5 minutes of your clock, then compare the signature timing-safe. Zero Hash documents the ±5 minute window but not whether the timestamp is in seconds or milliseconds, so normalize the value before comparing rather than assuming a unit:
const crypto = require('crypto');
// The unit of x-zh-hook-timestamp is not documented. A ~10-digit value is
// seconds, a ~13-digit value is milliseconds — normalize to ms either way.
function toMillis(timestamp) {
const value = Number(timestamp);
if (!Number.isFinite(value)) return NaN;
return Math.abs(value) < 1e11 ? value * 1000 : value;
}
function verifyZeroHash(rawBody, signature, timestamp, secret, toleranceMs = 5 * 60 * 1000) {
if (!signature || !timestamp) return false;
// Replay guard: accept either seconds or milliseconds.
const timestampMs = toMillis(timestamp);
if (!Number.isFinite(timestampMs)) return false;
if (Math.abs(Date.now() - timestampMs) > toleranceMs) return false;
const expected = crypto
.createHmac('sha256', secret)
.update(rawBody + timestamp, 'utf8') // payload + timestamp, no delimiter
.digest('hex');
try {
return crypto.timingSafeEqual(Buffer.from(expected), Buffer.from(signature));
} catch {
return false; // length mismatch => invalid
}
}
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 202 B
- examples/express/package.json 373 B
- examples/express/README.md 1.7 KB
- examples/express/src/index.js 5.6 KB runs code
- examples/express/test/webhook.test.js 8.0 KB runs code
- examples/fastapi/.env.example 133 B
- examples/fastapi/main.py 5.1 KB runs code
- examples/fastapi/README.md 1.9 KB
- examples/fastapi/requirements.txt 82 B
- examples/fastapi/test_webhook.py 8.7 KB runs code
- examples/nextjs/.env.example 133 B
- examples/nextjs/app/webhooks/zerohash/route.ts 4.9 KB runs code
- examples/nextjs/package.json 485 B
- examples/nextjs/README.md 1.8 KB
- examples/nextjs/test/webhook.test.ts 7.6 KB runs code
- examples/nextjs/vitest.config.ts 140 B runs code
- references/overview.md 5.1 KB
- references/setup.md 3.2 KB
- references/verification.md 7.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.
- yesterday First seen · 161 lines · 51 tokens per session scan A 88f559d2acbc
zerohash-webhooks is a skill published in the GitHub repository hookdeck/webhook-skills (84 stars, last pushed yesterday), licensed MIT. It adds 51 tokens to every session and 1,969 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-09-03.
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…