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/shipstation-webhooksnpx skills add hookdeck/webhook-skills --skill shipstation-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/shipstation-webhooks)<a href="https://agentmods.dev/skills/hookdeck/webhook-skills/shipstation-webhooks"><img src="https://agentmods.dev/badge/skills/hookdeck/webhook-skills/shipstation-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.00083 | $0.02050 |
| Opus 5 | $0.00042 | $0.01025 |
| Sonnet 5 | $0.00017 | $0.00410 |
| Haiku 4.5 | $0.00008 | $0.00205 |
Grade A, and why
shipstation-webhooks scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
const res = await fetch(resourceUrl, { headers: { Authorization: `Basic ${auth}` } }); How it starts
The opening of the file, as written. The whole thing — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ShipStation Webhooks
When to Use This Skill
- How do I receive ShipStation webhooks?
- How do I secure a ShipStation webhook endpoint when there is no signature?
- How do I fetch the
resource_urlfrom a ShipStation webhook payload? - How do I handle
ORDER_NOTIFY,SHIP_NOTIFY, orITEM_SHIP_NOTIFYevents? - Why does my ShipStation webhook only contain a
resource_urlandresource_type?
How ShipStation V1 Webhooks Work
This skill targets the ShipStation V1 API (ssapi.shipstation.com), the source you connect to Hookdeck.
Two things make V1 different from most webhook providers:
-
Thin payloads. ShipStation does not send the resource data. It POSTs a small JSON body with a URL you must fetch back:
{ "resource_url": "https://ssapi.shipstation.com/orders?...", "resource_type": "ORDER_NOTIFY" }You
GETresource_urlwith HTTP Basic auth (your API key : API secret) to get the actual orders/shipments. This authenticated fetch-back is the primary trust signal. -
No signature. V1 has no HMAC / no signing secret — there is nothing to verify cryptographically. Protect the endpoint by putting an unguessable secret token in the target URL (
https://you.com/webhooks/shipstation?token=…) and comparing it timing-safe on every request, over HTTPS. Combined with the authed fetch-back, this is the trust model.
Verification (core)
There is no signature. Verify the shared secret token from the query string (timing-safe), then fetch the real resource with Basic auth. Pass only ShipStation hosts to the fetch (SSRF guard).
const crypto = require('crypto');
// 1. Timing-safe compare of the ?token= query param against your secret
function verifyToken(provided, expected) {
if (!provided || !expected) return false;
const a = Buffer.from(provided);
const b = Buffer.from(expected);
return a.length === b.length && crypto.timingSafeEqual(a, b);
}
// resource_url hosts are reportedly numbered (ssapi1/ssapi2.shipstation.com) — match a pattern, not one host
const SHIPSTATION_HOST_RE = /^ssapi\d*\.shipstation\.com$/;
// 2. Fetch the thin payload's resource_url with Basic auth (API key : API secret)
async function fetchResource(resourceUrl, key, secret) {
if (!SHIPSTATION_HOST_RE.test(new URL(resourceUrl).hostname)) {
throw new Error('Refusing to fetch non-ShipStation host'); // SSRF guard
}
const auth = Buffer.from(`${key}:${secret}`).toString('base64');
const res = await fetch(resourceUrl, { headers: { Authorization: `Basic ${auth}` } });
if (res.status === 429) throw new Error(`Rate limited; reset ${res.headers.get('X-Rate-Limit-Reset')}s`);
if (!res.ok) throw new Error(`Fetch failed: ${res.status}`);
return res.json();
}
What ships with it
20 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 498 B
- examples/express/package.json 378 B
- examples/express/README.md 1.9 KB
- examples/express/src/index.js 4.4 KB runs code
- examples/express/test/webhook.test.js 4.5 KB runs code
- examples/fastapi/.env.example 458 B
- examples/fastapi/main.py 4.1 KB runs code
- examples/fastapi/README.md 2.0 KB
- examples/fastapi/requirements.txt 82 B
- examples/fastapi/test_webhook.py 4.8 KB runs code
- examples/nextjs/.env.example 458 B
- examples/nextjs/app/webhooks/shipstation/route.ts 2.5 KB runs code
- examples/nextjs/app/webhooks/shipstation/verify.ts 2.0 KB runs code
- examples/nextjs/package.json 490 B
- examples/nextjs/README.md 1.9 KB
- examples/nextjs/test/webhook.test.ts 3.2 KB runs code
- examples/nextjs/vitest.config.ts 140 B runs code
- references/overview.md 3.6 KB
- references/setup.md 3.4 KB
- references/verification.md 6.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.
- yesterday First seen · 159 lines · 83 tokens per session scan A cba726449fc6
shipstation-webhooks is a skill published in the GitHub repository hookdeck/webhook-skills (84 stars, last pushed yesterday), licensed MIT. It adds 83 tokens to every session and 2,050 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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…
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…