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/shipbob-webhooksnpx skills add hookdeck/webhook-skills --skill shipbob-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/shipbob-webhooks)<a href="https://agentmods.dev/skills/hookdeck/webhook-skills/shipbob-webhooks"><img src="https://agentmods.dev/badge/skills/hookdeck/webhook-skills/shipbob-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.00061 | $0.01842 |
| Opus 5 | $0.00030 | $0.00921 |
| Sonnet 5 | $0.00012 | $0.00368 |
| Haiku 4.5 | $0.00006 | $0.00184 |
Grade A, and why
shipbob-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
80% identical to adyen-webhooks — 172 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 — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ShipBob Webhooks
When to Use This Skill
- Setting up ShipBob webhook handlers
- Debugging ShipBob signature verification failures
- Understanding ShipBob event types (topics) and payloads
- Handling fulfillment, shipment, return, receiving (WRO), or billing events
Verification (core)
ShipBob signs webhooks with the Standard Webhooks
scheme (the same fields Svix uses). It sends three headers — webhook-id,
webhook-timestamp, and webhook-signature — and the event topic in a
separate x-webhook-topic header (e.g. order.shipped).
The signature is HMAC-SHA256(secret, "{webhook-id}.{webhook-timestamp}.{body}"),
base64-encoded. The signing secret is whsec_<base64> — strip the whsec_
prefix and base64-decode the remainder to get the raw HMAC key. Always verify
against the raw, unmodified request body (don't JSON.parse first).
webhook-signature holds space-delimited versioned signatures (v1,<sig>);
compare against the v1 entry with a timing-safe comparison.
Node (via the standardwebhooks package, which handles the secret decode and
multi-signature parsing for you):
const { Webhook } = require('standardwebhooks');
const wh = new Webhook(process.env.SHIPBOB_WEBHOOK_SECRET); // whsec_...
// rawBody is a Buffer/string; headers use the Standard Webhooks names
const event = wh.verify(rawBody, {
'webhook-id': req.headers['webhook-id'],
'webhook-timestamp': req.headers['webhook-timestamp'],
'webhook-signature': req.headers['webhook-signature'],
}); // throws WebhookVerificationError on tampering or a stale timestamp
const topic = req.headers['x-webhook-topic']; // e.g. "order.shipped"
Python (manual — there is no official ShipBob SDK):
import hmac, hashlib, base64
def verify(body: bytes, webhook_id, webhook_timestamp, webhook_signature, secret):
signed = f"{webhook_id}.{webhook_timestamp}.{body.decode()}".encode()
key = base64.b64decode(secret.split("_", 1)[1]) # strip 'whsec_' then base64-decode
expected = base64.b64encode(hmac.new(key, signed, hashlib.sha256).digest()).decode()
sent = [s.split(",", 1)[1] for s in webhook_signature.split(" ") if "," in s]
return any(hmac.compare_digest(expected, s) for s in sent) # timing-safe
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 324 B
- examples/express/package.json 497 B
- examples/express/README.md 1.4 KB
- examples/express/src/index.js 3.7 KB runs code
- examples/express/test/webhook.test.js 6.6 KB runs code
- examples/fastapi/.env.example 253 B
- examples/fastapi/main.py 4.6 KB runs code
- examples/fastapi/README.md 1.5 KB
- examples/fastapi/requirements.txt 92 B
- examples/fastapi/test_webhook.py 5.2 KB runs code
- examples/nextjs/.env.example 253 B
- examples/nextjs/app/webhooks/shipbob/route.ts 2.8 KB runs code
- examples/nextjs/package.json 593 B
- examples/nextjs/README.md 1.3 KB
- examples/nextjs/test/webhook.test.ts 5.8 KB runs code
- examples/nextjs/vitest.config.ts 162 B runs code
- references/overview.md 3.9 KB
- references/setup.md 2.8 KB
- references/verification.md 4.9 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 · 143 lines · 61 tokens per session scan A c93d77468f7f
shipbob-webhooks is a skill published in the GitHub repository hookdeck/webhook-skills (84 stars, last pushed yesterday), licensed MIT. It adds 61 tokens to every session and 1,842 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 80% identical to adyen-webhooks, differing in 172 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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…