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/zendesk-webhooksnpx skills add hookdeck/webhook-skills --skill zendesk-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/zendesk-webhooks)<a href="https://agentmods.dev/skills/hookdeck/webhook-skills/zendesk-webhooks"><img src="https://agentmods.dev/badge/skills/hookdeck/webhook-skills/zendesk-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.00063 | $0.01556 |
| Opus 5 | $0.00032 | $0.00778 |
| Sonnet 5 | $0.00013 | $0.00311 |
| Haiku 4.5 | $0.00006 | $0.00156 |
Grade A, and why
zendesk-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.
This is a copy
77% identical to adyen-webhooks — 171 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 — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Zendesk Webhooks
When to Use This Skill
- Setting up Zendesk webhook handlers
- Debugging Zendesk signature verification failures
- Understanding Zendesk event subscriptions vs. trigger/automation webhooks
- Handling ticket, user, or organization events like
zen:event-type:ticket.created
Verification (core)
Zendesk signs every webhook with HMAC-SHA256, base64-encoded. The signed
message is the timestamp concatenated directly with the raw request body
(no separator): base64(HMAC_SHA256(timestamp + body)). Zendesk does not
follow the Standard Webhooks spec and ships no official verification SDK, so
verify manually with the language's crypto primitives.
Two headers are sent:
X-Zendesk-Webhook-Signature— the base64 signatureX-Zendesk-Webhook-Signature-Timestamp— the timestamp that is prepended to the body
Use the raw body — don't JSON.parse first. Some requests (e.g. GET/DELETE
methods on a webhook) have no body, so account for an empty body.
const crypto = require('crypto');
function verifyZendeskWebhook(rawBody, signature, timestamp, secret) {
const hmac = crypto.createHmac('sha256', secret);
hmac.update(timestamp); // timestamp first...
hmac.update(rawBody); // ...then the raw body (Buffer), no separator
const expected = hmac.digest('base64');
try {
return crypto.timingSafeEqual(Buffer.from(expected), Buffer.from(signature));
} catch {
return false; // length mismatch = invalid
}
}
The signing secret comes from GET /api/v2/webhooks/{webhook_id}/signing_secret
(or Admin Center → the webhook → Reveal secret). Test webhooks (before
creation) always use the static secret dGhpc19zZWNyZXRfaXNfZm9yX3Rlc3Rpbmdfb25seQ==.
For complete handlers with route wiring, event dispatch, and tests, see:
Two Webhook Models
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 203 B
- examples/express/package.json 370 B
- examples/express/README.md 1.2 KB
- examples/express/src/index.js 4.6 KB runs code
- examples/express/test/webhook.test.js 6.3 KB runs code
- examples/fastapi/.env.example 203 B
- examples/fastapi/main.py 3.6 KB runs code
- examples/fastapi/README.md 1.6 KB
- examples/fastapi/requirements.txt 82 B
- examples/fastapi/test_webhook.py 6.5 KB runs code
- examples/nextjs/.env.example 203 B
- examples/nextjs/app/webhooks/zendesk/route.ts 3.6 KB runs code
- examples/nextjs/package.json 482 B
- examples/nextjs/README.md 1.5 KB
- examples/nextjs/test/webhook.test.ts 3.9 KB runs code
- examples/nextjs/vitest.config.ts 140 B runs code
- references/overview.md 3.1 KB
- references/setup.md 3.2 KB
- references/verification.md 4.0 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 · 136 lines · 63 tokens per session scan A 70b8d25b6130
zendesk-webhooks is a skill published in the GitHub repository hookdeck/webhook-skills (84 stars, last pushed yesterday), licensed MIT. It adds 63 tokens to every session and 1,556 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 77% identical to adyen-webhooks, differing in 171 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…