commercelayer-webhooks

Instructions for receiving and checking Commerce Layer webhooks, which are messages sent by an online commerce system when events such as orders or shipments occur. It explains how to verify the sender using the signature on the original request body.

In plain words
What is it for?
Use it to build Commerce Layer callback endpoints, verify X-CommerceLayer-Signature values, and handle order placement, approval, payment, and shipment events.
Why use it?
It helps prevent accepting forged or incorrectly processed event messages. It also addresses signature failures caused by changing the request body before checking it.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/hookdeck/webhook-skills/commercelayer-webhooks
Any agent
npx skills add hookdeck/webhook-skills --skill commercelayer-webhooks
Clone the repo
git clone --depth 1 https://github.com/hookdeck/webhook-skills

Made for: Claude Code, Codex.

Per session 52 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,716 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 3d ago against content hash dfc1d7c01442, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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.

The scan reads SKILL.md. This mod also ships 7 executable files (examples/express/src/index.js, examples/express/test/webhook.test.js, examples/fastapi/main.py, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

skills/commercelayer-webhooks/SKILL.md · 156 lines

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, or orders.pay events?
  • Why is my Commerce Layer X-CommerceLayer-Signature verification 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:

Read the full file on GitHub · 156 lines

Changes

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.

  1. 3d ago First seen · 156 lines · 52 tokens per session scan A dfc1d7c01442

Subscribe to this mod's changes

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.

Related

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.

ReScienceLab/opc-skills · 48 tokens

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.

cwinvestments/memstack · 65 tokens

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…

rajitsaha/100xprism · 84 tokens

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.

Dkm0315/frappe-agent · 49 tokens

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.

TheWinci/mimirs · 38 tokens

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.

TheWinci/mimirs · 60 tokens