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/coinbase-commerce-webhooksnpx skills add hookdeck/webhook-skills --skill coinbase-commerce-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/coinbase-commerce-webhooks)<a href="https://agentmods.dev/skills/hookdeck/webhook-skills/coinbase-commerce-webhooks"><img src="https://agentmods.dev/badge/skills/hookdeck/webhook-skills/coinbase-commerce-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.00066 | $0.01305 |
| Opus 5 | $0.00033 | $0.00652 |
| Sonnet 5 | $0.00013 | $0.00261 |
| Haiku 4.5 | $0.00007 | $0.00130 |
Grade A, and why
coinbase-commerce-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 4d 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.
This is a copy
81% identical to adyen-webhooks — 149 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Coinbase Commerce Webhooks
When to Use This Skill
- Setting up Coinbase Commerce webhook handlers for cryptocurrency payments
- Debugging
X-CC-Webhook-Signatureverification failures - Understanding Coinbase Commerce charge event types and payloads
- Handling
charge:confirmed,charge:failed, orcharge:pendingevents
Verification (core)
Coinbase Commerce signs the raw request body with HMAC-SHA256 keyed on your
webhook shared secret and sends the hex digest in the X-CC-Webhook-Signature
header. Verify against the raw body (never the parsed JSON) and compare
timing-safe. The event object is nested under the event key in the body.
Node — use the official coinbase-commerce-node SDK:
const { Webhook } = require('coinbase-commerce-node');
// Throws SignatureVerificationError on mismatch; returns the verified event.
// rawBody MUST be the raw request body string, not re-serialized JSON.
const event = Webhook.verifyEventBody(rawBody, signature, sharedSecret);
console.log(event.type, event.data.id); // e.g. "charge:confirmed"
Manual (any language) — HMAC-SHA256 hex of the raw body, timing-safe compare:
import hmac, hashlib
def verify(raw_body: bytes, signature: str, secret: str) -> bool:
expected = hmac.new(secret.encode(), raw_body, hashlib.sha256).hexdigest()
return hmac.compare_digest(expected, signature or "")
For complete handlers with route wiring, event dispatch, and tests, see:
Common Event Types
| Event | Triggered When |
|---|---|
charge:created |
A new charge is created |
charge:pending |
Customer paid; payment detected on-chain but not yet confirmed |
charge:confirmed |
Payment confirmed — the charge is complete |
charge:failed |
The charge failed or expired without full payment |
charge:delayed |
Payment arrived late or was underpaid/overpaid |
charge:resolved |
A previously delayed charge has been resolved |
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 230 B
- examples/express/package.json 430 B
- examples/express/README.md 1.6 KB
- examples/express/src/index.js 2.9 KB runs code
- examples/express/test/webhook.test.js 3.6 KB runs code
- examples/fastapi/.env.example 161 B
- examples/fastapi/main.py 2.8 KB runs code
- examples/fastapi/README.md 1.9 KB
- examples/fastapi/requirements.txt 82 B
- examples/fastapi/test_webhook.py 4.1 KB runs code
- examples/nextjs/.env.example 161 B
- examples/nextjs/app/webhooks/coinbase-commerce/route.ts 2.3 KB runs code
- examples/nextjs/package.json 541 B
- examples/nextjs/README.md 1.6 KB
- examples/nextjs/test/webhook.test.ts 3.4 KB runs code
- examples/nextjs/types/coinbase-commerce-node.d.ts 383 B runs code
- examples/nextjs/vitest.config.ts 140 B runs code
- references/overview.md 3.1 KB
- references/setup.md 1.9 KB
- references/verification.md 4.0 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.
- 4d ago First seen · 120 lines · 66 tokens per session scan A 7aa0deb74998
coinbase-commerce-webhooks is a skill published in the GitHub repository hookdeck/webhook-skills (84 stars, last pushed today), licensed MIT. It adds 66 tokens to every session and 1,305 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 81% identical to adyen-webhooks, differing in 149 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…