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/ethoca-webhooksnpx skills add hookdeck/webhook-skills --skill ethoca-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.00059 | $0.01848 |
| Opus 5 | $0.00030 | $0.00924 |
| Sonnet 5 | $0.00012 | $0.00370 |
| Haiku 4.5 | $0.00006 | $0.00185 |
Grade A, and why
ethoca-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 2d 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 — 185 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 — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ethoca Webhooks
Ethoca (a Mastercard company) delivers Alerts — early fraud and dispute notifications from issuers — to merchants. The Alerts Push API HTTPS-POSTs JSON to an endpoint you register with the Ethoca Customer Delivery Team.
When to Use This Skill
- How do I receive Ethoca Alerts webhooks (Push API)?
- How do I secure an Ethoca webhook endpoint without a signature header?
- How do I handle Ethoca fraud and dispute alerts?
- Why is there no
X-Ethoca-Signature/ HMAC header to verify? - How does Ethoca mTLS (MSSL) delivery work?
Verification (core)
There is NO per-message HMAC/signature header on Ethoca Push API alerts. Do
not look for X-Ethoca-Signature or a Standard Webhooks header — none exists.
Trust is established primarily by the transport:
- Transport — mutual TLS (MSSL) — the definitive check. Ethoca presents a client certificate; your server must trust the Entrust CA and require a client cert. This is enforced at your TLS terminator / load balancer, not in app code, and is the actual mechanism that authenticates the delivery.
- Application — HTTP Basic Auth (OPTIONAL). If you agree Basic Auth
credentials with the Ethoca Customer Delivery Team at onboarding, Ethoca sends
Authorization: Basic base64(username:password)and your handler checks it. Whether Ethoca sends Basic Auth is not guaranteed by the API — an endpoint secured by mTLS alone may receive noAuthorizationheader.
An IP allowlist of Ethoca's egress ranges is a recommended additional layer.
Enforce Basic Auth only when credentials are configured — if none are set,
accept the delivery and rely on mTLS rather than returning 401. When
configured, verify the credentials with a timing-safe comparison. Node:
const crypto = require('crypto');
function safeEqual(a, b) {
const ab = Buffer.from(a), bb = Buffer.from(b);
return ab.length === bb.length && crypto.timingSafeEqual(ab, bb);
}
function verifyEthocaAuth(authHeader, username, password) {
if (!authHeader || !authHeader.startsWith('Basic ')) return false;
const decoded = Buffer.from(authHeader.slice(6), 'base64').toString('utf-8');
const i = decoded.indexOf(':');
if (i === -1) return false;
return safeEqual(decoded.slice(0, i), username) &&
safeEqual(decoded.slice(i + 1), password);
}
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 433 B
- examples/express/package.json 375 B
- examples/express/README.md 1.5 KB
- examples/express/src/index.js 4.7 KB runs code
- examples/express/test/webhook.test.js 3.9 KB runs code
- examples/fastapi/.env.example 433 B
- examples/fastapi/main.py 3.8 KB runs code
- examples/fastapi/README.md 1.7 KB
- examples/fastapi/requirements.txt 82 B
- examples/fastapi/test_webhook.py 3.9 KB runs code
- examples/nextjs/.env.example 433 B
- examples/nextjs/app/webhooks/ethoca/route.ts 3.6 KB runs code
- examples/nextjs/package.json 487 B
- examples/nextjs/README.md 1.6 KB
- examples/nextjs/test/webhook.test.ts 3.5 KB runs code
- examples/nextjs/vitest.config.ts 140 B runs code
- references/overview.md 4.3 KB
- references/setup.md 3.8 KB
- references/verification.md 6.4 KB
- TODO.md 2.4 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.
- 2d ago First seen · 150 lines · 59 tokens per session scan A 0548596ffdd4
ethoca-webhooks is a skill published in the GitHub repository hookdeck/webhook-skills (84 stars, last pushed 6d ago), licensed MIT. It adds 59 tokens to every session and 1,848 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 185 lines, and is treated as a copy.
Other skills, from other repositories
startup-ceo
CEO coordinator that dispatches research, strategy, finance, and writer specialists via A2A and synthesizes their findings into a GO/NO-GO investment briefing. Use for multi-agent advisory workflows.
finance-agent
Financial analyst for startup economics — TAM/SAM/SOM, revenue projections, burn rate, runway, and break-even. Use when building financial models or evaluating investment cases.
billing-agent
Billing specialist for invoices, payments, refunds, and plan changes. Use when customers ask about charges, billing inquiries, or subscription management; typically reached via handoff from the support agent.
memstack-business-invoice-generator
Use this skill when the user says 'invoice', 'generate invoice', 'create invoice', 'bill client', 'line items', 'payment terms', or needs professional invoices with tax calculations and payment instructions. Do NOT use for contracts or financial projections.
memstack-business-financial-model
Use this skill when the user says 'financial model', 'projections', 'revenue forecast', 'unit economics', 'break-even', 'cash flow', or mentions MRR, churn, CAC, LTV, or runway. Builds monthly projections with scenario modeling. Do NOT use for pricing strategy or invoice generation.
memstack-business-freelancer-toolkit
Use when the user says 'track my time', 'freelancer invoice', 'billable hours', 'time tracking', 'freelance finances', 'client billing', 'project hours', or needs invoicing, time tracking, or analytics patterns for freelance work. Do NOT use for general invoice templates or proposal writing.