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 onfleet-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/onfleet-webhooks)<a href="https://agentmods.dev/skills/hookdeck/webhook-skills/onfleet-webhooks"><img src="https://agentmods.dev/badge/skills/hookdeck/webhook-skills/onfleet-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/onfleet-webhooks"><img src="https://agentmods.dev/badge/skills/hookdeck/webhook-skills/onfleet-webhooks.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00081 | $0.02228 |
| Opus 5.5 | $0.00032 | $0.00891 |
| Sonnet 5.5 | $0.00016 | $0.00446 |
| Haiku 4.5 | $0.00008 | $0.00223 |
Grade A, and why
onfleet-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 today.
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
78% identical to adyen-webhooks — 232 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 — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Onfleet Webhooks
Onfleet is a last-mile delivery platform. Each Onfleet
webhook targets one trigger (task started, task completed, worker on duty,
and so on). When you create a webhook, Onfleet first sends an unsigned
GET ?check=<random_string> request to validate the URL. After that, every
event arrives as a signed POST with an X-Onfleet-Signature header.
When to Use This Skill
- How do I receive Onfleet webhooks?
- Why won't Onfleet save my webhook URL? (the
GET ?check=handshake) - How do I verify the
X-Onfleet-Signatureheader? - Why does my Onfleet signature never match? (the secret is hex)
- How do I handle
taskCompleted,taskFailed,taskEtaorworkerDuty?
Validation Handshake
When a webhook is created, Onfleet sends GET <your url>?check=<random_string>.
Reply 200 with the exact string as a plain-text body. Onfleet doesn't
accept a 204, and the request is not signed, so don't run signature
verification on it. The string changes on every attempt.
app.get('/webhooks/onfleet', (req, res) => {
const check = req.query.check;
if (typeof check !== 'string') {
return res.status(400).type('text/plain').send('Missing check parameter');
}
res.status(200).type('text/plain').send(check);
});
Signature Verification (core)
| Header | X-Onfleet-Signature |
| Algorithm | HMAC-SHA512, hex digest |
| Key | The organisation's webhook secret, hex-decoded to bytes |
| Signed content | The raw request body bytes. No timestamp, no prefix |
The secret is a hex string. Use it as an HMAC key only after hex-decoding it. If you pass the string as-is, you get a well-formed digest that never matches.
const crypto = require('crypto');
function verifyOnfleetSignature(rawBody, signatureHeader, secretHex) {
if (!signatureHeader) {
return { valid: false, error: 'Missing X-Onfleet-Signature header' };
}
const expected = crypto
.createHmac('sha512', Buffer.from(secretHex, 'hex'))
.update(rawBody)
.digest('hex');
const received = Buffer.from(signatureHeader.trim().toLowerCase(), 'utf8');
const computed = Buffer.from(expected, 'utf8');
// timingSafeEqual throws on unequal lengths, so check first.
if (received.length !== computed.length) {
return { valid: false, error: 'Invalid signature' };
}
if (!crypto.timingSafeEqual(received, computed)) {
return { valid: false, error: 'Invalid signature' };
}
return { valid: true };
}
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 429 B
- examples/express/package.json 420 B
- examples/express/README.md 2.4 KB
- examples/express/src/index.js 7.8 KB runs code
- examples/express/test/webhook.test.js 8.9 KB runs code
- examples/fastapi/.env.example 429 B
- examples/fastapi/main.py 9.0 KB runs code
- examples/fastapi/README.md 2.5 KB
- examples/fastapi/requirements.txt 82 B
- examples/fastapi/test_webhook.py 8.7 KB runs code
- examples/nextjs/.env.example 373 B
- examples/nextjs/app/webhooks/onfleet/route.ts 8.5 KB runs code
- examples/nextjs/package.json 541 B
- examples/nextjs/README.md 2.4 KB
- examples/nextjs/test/webhook.test.ts 9.2 KB runs code
- examples/nextjs/vitest.config.ts 121 B runs code
- references/overview.md 6.0 KB
- references/setup.md 4.0 KB
- references/verification.md 5.7 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.
- today First seen · 189 lines · 81 tokens per session scan A 0a44fd9bb87c
onfleet-webhooks is a skill published in the GitHub repository hookdeck/webhook-skills (92 stars, last pushed yesterday), licensed MIT. It adds 81 tokens to every session and 2,228 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 78% identical to adyen-webhooks, differing in 232 lines, and is treated as a copy.
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…