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/wix-webhooksnpx skills add hookdeck/webhook-skills --skill wix-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/wix-webhooks)<a href="https://agentmods.dev/skills/hookdeck/webhook-skills/wix-webhooks"><img src="https://agentmods.dev/badge/skills/hookdeck/webhook-skills/wix-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.00077 | $0.02027 |
| Opus 5 | $0.00039 | $0.01014 |
| Sonnet 5 | $0.00015 | $0.00405 |
| Haiku 4.5 | $0.00008 | $0.00203 |
Grade A, and why
wix-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.
How it starts
The opening of the file, as written. The whole thing — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Wix Webhooks
When to Use This Skill
- How do I receive Wix webhooks in a self-hosted app?
- How do I verify Wix webhook signatures (the JWT)?
- Where do I get my Wix public key to verify webhooks?
- How do I handle
wix.ecom.v1.order_created/order_approved/order_canceledevents? - Why is my Wix webhook JWT verification failing?
How Wix Webhooks Work
Wix delivers each webhook as an HTTP POST whose entire request body is a signed JWT (RS256), signed by Wix. There are no X-Wix-Signature/HMAC headers and it is not Standard Webhooks — verification means validating the JWT with your app's public key.
- Get your public key from the app dashboard → Custom Apps → your app → Webhooks → "Get Public Key" (also under View ID & keys). It is per-app; there is no global JWKS endpoint.
- Verify against the raw, unparsed body. Re-serializing the JSON breaks the signature.
- The decoded JWT is a nested envelope: outer
{ data, iat, exp }→datais a JSON string → parse it to{ eventType, instanceId, data }→ parse the innerdatastring to get the entity/event payload.
Verification (core)
Node.js — official @wix/sdk verifies (RS256, via jose) and decodes in one call. Pass the raw text body:
import { AppStrategy, createClient } from '@wix/sdk';
import { orders } from '@wix/ecom';
const client = createClient({
auth: AppStrategy({
appId: process.env.WIX_APP_ID,
publicKey: process.env.WIX_PUBLIC_KEY.replace(/\\n/g, '\n'), // PEM, or base64-encoded PEM
}),
modules: { orders },
});
// Register typed handlers up front...
client.orders.onOrderCanceled((event) => {
console.log('Order canceled', event.metadata.entityId, 'event', event.metadata._id);
});
// ...then verify + dispatch the raw JWT body (throws if the signature/exp is invalid):
await client.webhooks.process(rawBody);
Python (no official server SDK) — verify the JWT manually with PyJWT + your public key:
import json, jwt # PyJWT
def verify_and_decode(raw_body: bytes, public_key: str) -> dict:
decoded = jwt.decode(raw_body, public_key, algorithms=["RS256"]) # raises on bad signature/exp
event = json.loads(decoded["data"]) # -> { eventType, instanceId, data: "<json>" }
event["entity"] = json.loads(event["data"]) # inner event/entity payload (has id, entityId, ...)
return event
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 462 B
- examples/express/package.json 433 B
- examples/express/README.md 2.0 KB
- examples/express/src/index.js 3.4 KB runs code
- examples/express/test/webhook.test.js 4.9 KB runs code
- examples/fastapi/.env.example 347 B
- examples/fastapi/main.py 3.3 KB runs code
- examples/fastapi/README.md 2.1 KB
- examples/fastapi/requirements.txt 117 B
- examples/fastapi/test_webhook.py 4.6 KB runs code
- examples/nextjs/.env.example 393 B
- examples/nextjs/app/webhooks/wix/route.ts 3.0 KB runs code
- examples/nextjs/package.json 545 B
- examples/nextjs/README.md 2.3 KB
- examples/nextjs/test/webhook.test.ts 4.3 KB runs code
- examples/nextjs/vitest.config.ts 140 B runs code
- references/overview.md 4.5 KB
- references/setup.md 2.9 KB
- references/verification.md 5.5 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 · 148 lines · 77 tokens per session scan A d2925b60ef45
wix-webhooks is a skill published in the GitHub repository hookdeck/webhook-skills (84 stars, last pushed yesterday), licensed MIT. It adds 77 tokens to every session and 2,027 once invoked, about $0.0004 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-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…
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…