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/commercelayer-webhooksnpx skills add hookdeck/webhook-skills --skill commercelayer-webhooksgit clone --depth 1 https://github.com/hookdeck/webhook-skillsWhat 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.00052 | $0.01716 |
| Opus 5 | $0.00026 | $0.00858 |
| Sonnet 5 | $0.00010 | $0.00343 |
| Haiku 4.5 | $0.00005 | $0.00172 |
Grade A, and why
commercelayer-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 3d ago.
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 — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commerce Layer Webhooks
When to Use This Skill
- How do I receive Commerce Layer webhooks?
- How do I verify Commerce Layer webhook signatures?
- How do I handle
orders.place,orders.approve, ororders.payevents? - Why is my Commerce Layer
X-CommerceLayer-Signatureverification failing? - Setting up a Commerce Layer callback endpoint for order/shipment events
Verification (core)
Commerce Layer signs the raw request body with HMAC-SHA256 keyed on the
webhook's shared_secret and sends the digest as base64 in the
X-CommerceLayer-Signature header. The triggering topic is in X-CommerceLayer-Topic.
The shared_secret is returned once, in the response when you create the webhook
(POST /api/webhooks) — it is not the same as your API credentials.
Read the raw body, NOT the parsed one. Re-serializing parsed JSON changes bytes (key order, whitespace) and breaks the signature. Commerce Layer has no SDK verify helper, so verify manually (this matches the official docs example).
Node:
const crypto = require('crypto');
function verifyCommerceLayerSignature(rawBody, signature, sharedSecret) {
if (!signature) return false;
const expected = crypto
.createHmac('sha256', sharedSecret)
.update(rawBody) // rawBody is a Buffer/string — never JSON.parse first
.digest('base64');
try {
return crypto.timingSafeEqual(Buffer.from(signature), Buffer.from(expected));
} catch {
return false; // length mismatch = invalid
}
}
Python:
import hmac, hashlib, base64
def verify_commercelayer_signature(raw_body: bytes, signature: str, shared_secret: str) -> bool:
if not signature:
return False
expected = base64.b64encode(
hmac.new(shared_secret.encode(), raw_body, hashlib.sha256).digest()
).decode()
return hmac.compare_digest(signature, expected)
For complete handlers with route wiring, event dispatch, and tests, see:
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 256 B
- examples/express/package.json 420 B
- examples/express/README.md 1.5 KB
- examples/express/src/index.js 3.9 KB runs code
- examples/express/test/webhook.test.js 4.2 KB runs code
- examples/fastapi/.env.example 177 B
- examples/fastapi/main.py 3.1 KB runs code
- examples/fastapi/README.md 1.7 KB
- examples/fastapi/requirements.txt 82 B
- examples/fastapi/test_webhook.py 4.3 KB runs code
- examples/nextjs/.env.example 177 B
- examples/nextjs/app/webhooks/commercelayer/route.ts 3.0 KB runs code
- examples/nextjs/package.json 532 B
- examples/nextjs/README.md 1.6 KB
- examples/nextjs/test/webhook.test.ts 3.4 KB runs code
- examples/nextjs/vitest.config.ts 140 B runs code
- references/overview.md 3.9 KB
- references/setup.md 3.8 KB
- references/verification.md 4.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.
- 3d ago First seen · 156 lines · 52 tokens per session scan A dfc1d7c01442
commercelayer-webhooks is a skill published in the GitHub repository hookdeck/webhook-skills (84 stars, last pushed 6d ago), licensed MIT. It adds 52 tokens to every session and 1,716 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-08-30.
Other skills, from other repositories
domain-hunter
Search domains, compare prices, find promo codes, get purchase recommendations. Use when user wants to buy a domain, check domain prices, find domain deals, compare registrars, or search for .ai/.com domains.
memstack-content-product-description
Use this skill when the user says 'product description', 'product listing', 'product copy', 'Amazon listing', 'Shopify listing', 'e-commerce copy', or needs conversion-optimized product descriptions with benefit-driven headlines and platform-specific SEO. Do NOT use for pricing strategy or sales funnels.
form-cro
When the user wants to optimize any form that is NOT signup/registration — lead capture, contact, demo request, application, survey, or checkout forms; "form friction," "form completion rate," "form abandonment," "too many fields," "nobody fills out our form." For signup/registration forms, see signup-flow-cro. For…
frappe-payments
Frappe Payments and ERPNext payment workflow guidance for payment gateways, payment requests, subscriptions, invoices, reconciliation, webhooks, and secure checkout flows. Use when work touches payments in Frappe or ERPNext.
wiki
Rebuild a flow-first project wiki using the mimirs wiki MCP tool. Use when the user asks to generate, rebuild, refresh, or write the wiki for a codebase.
scout
Research the web for solutions, competitors, alternatives, or prior art for a decision facing this project — then store the findings in project memory so they survive the session. Use when choosing a library or approach, comparing tools, checking what others do, or evaluating whether to build vs adopt.