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 skills add hookdeck/webhook-skills --skill ebay-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/ebay-webhooks)<a href="https://agentmods.dev/skills/hookdeck/webhook-skills/ebay-webhooks"><img src="https://agentmods.dev/badge/skills/hookdeck/webhook-skills/ebay-webhooks/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/hookdeck/webhook-skills/ebay-webhooks"><img src="https://agentmods.dev/badge/skills/hookdeck/webhook-skills/ebay-webhooks.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00069 | $0.01994 |
| Opus 5.5 | $0.00028 | $0.00798 |
| Sonnet 5.5 | $0.00014 | $0.00399 |
| Haiku 4.5 | $0.00007 | $0.00199 |
Grade A, and why
ebay-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 1mo 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 — 192 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 — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
eBay Webhooks
When to Use This Skill
- How do I receive eBay webhooks (notifications)?
- How do I pass eBay's endpoint challenge validation (
challenge_code)? - How do I verify the
x-ebay-signatureheader (ECDSA)? - How do I use the eBay
getPublicKeyendpoint and cache the public key? - How do I handle
MARKETPLACE_ACCOUNT_DELETION(marketplace account deletion / closure) notifications? - Why is my eBay signature verification failing?
How eBay Webhooks Differ From Most Providers
eBay does not use HMAC with a shared secret, and does not follow the Standard Webhooks spec. Two distinct mechanisms are involved:
- Endpoint challenge (one-time, on save) — When you register or update a
destination, eBay sends
GET https://<your-endpoint>?challenge_code=.... You must respond HTTP 200 with JSON{"challengeResponse":"<hex>"}where the hex is the SHA-256 hash of exactly `challengeCode + verificationToken- endpoint` — in that order. The order is mandatory.
- Per-notification signature (ECDSA) — Every notification carries an
x-ebay-signatureheader: a Base64-encoded JSON object with fieldsalg,kid,signature, anddigest. Use thekidto fetch the matching public key viagetPublicKey, then verify the ECDSA signature over the raw request body. Cache the public key ~1 hour (keyed bykid).
Verification (core)
Endpoint challenge — deterministic SHA-256, no crypto keys needed:
const crypto = require('crypto');
function challengeResponse(challengeCode, verificationToken, endpoint) {
// ORDER IS MANDATORY: challengeCode + verificationToken + endpoint
const hash = crypto.createHash('sha256');
hash.update(challengeCode);
hash.update(verificationToken);
hash.update(endpoint);
return hash.digest('hex'); // return as { challengeResponse: <hex> } with HTTP 200
}
Per-notification signature — ECDSA over the raw body, key fetched by kid:
async function verifyEbaySignature(rawBody, signatureHeader, getPublicKey) {
if (!signatureHeader) return false;
let sig;
try { sig = JSON.parse(Buffer.from(signatureHeader, 'base64').toString('utf8')); }
catch { return false; } // { alg, kid, signature, digest }
if (!sig.kid || !sig.signature) return false;
const pem = await getPublicKey(sig.kid); // cache ~1h, keyed by kid
const verifier = crypto.createVerify('sha1'); // eBay signs ECDSA with SHA-1
verifier.update(rawBody); // RAW body bytes — do not re-serialize
verifier.end();
try { return verifier.verify(pem, sig.signature, 'base64'); }
catch { return false; }
}
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 735 B
- examples/express/package.json 479 B
- examples/express/README.md 2.6 KB
- examples/express/src/index.js 6.4 KB runs code
- examples/express/test/webhook.test.js 5.6 KB runs code
- examples/fastapi/.env.example 679 B
- examples/fastapi/main.py 6.2 KB runs code
- examples/fastapi/README.md 2.1 KB
- examples/fastapi/requirements.txt 103 B
- examples/fastapi/test_webhook.py 5.2 KB runs code
- examples/nextjs/.env.example 679 B
- examples/nextjs/app/webhooks/ebay/route.ts 5.9 KB runs code
- examples/nextjs/package.json 555 B
- examples/nextjs/README.md 2.0 KB
- examples/nextjs/test/webhook.test.ts 5.6 KB runs code
- examples/nextjs/vitest.config.ts 140 B runs code
- references/overview.md 3.9 KB
- references/setup.md 3.9 KB
- references/verification.md 8.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.
- 1mo ago First seen · 161 lines · 69 tokens per session scan A 690e3a93060a
ebay-webhooks is a skill published in the GitHub repository hookdeck/webhook-skills (92 stars, last pushed yesterday), licensed MIT. It adds 69 tokens to every session and 1,994 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 81% identical to adyen-webhooks, differing in 192 lines, and is treated as a copy.
Other skills, from other repositories
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…