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/bridge-xyz-webhooksnpx skills add hookdeck/webhook-skills --skill bridge-xyz-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/bridge-xyz-webhooks)<a href="https://agentmods.dev/skills/hookdeck/webhook-skills/bridge-xyz-webhooks"><img src="https://agentmods.dev/badge/skills/hookdeck/webhook-skills/bridge-xyz-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.1 | $0.00064 | $0.01732 |
| Opus 5 | $0.00032 | $0.00866 |
| Sonnet 5 | $0.00013 | $0.00346 |
| Haiku 4.5 | $0.00006 | $0.00173 |
Grade A, and why
bridge-xyz-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 6d 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.
How it starts
The opening of the file, as written. The whole thing — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bridge (bridge.xyz) Webhooks
Bridge is a stablecoin orchestration platform (customers, KYC links, transfers, virtual accounts, cards). It delivers webhooks signed with an RSA-SHA256 signature and verified against a per-endpoint PEM public key returned when you create/update the webhook — there is no HMAC shared secret and no official SDK.
When to Use This Skill
- How do I receive Bridge webhooks?
- How do I verify the Bridge
X-Webhook-Signatureheader? - Why is my Bridge webhook signature verification failing?
- How do I handle
customer.updated,kyc_link.updated,transfer.updated, orvirtual_account.activityevents? - How do I create and enable a Bridge webhook endpoint via the API?
Verification (core)
Bridge sends X-Webhook-Signature: t=<timestamp_ms>,v0=<base64_signature>. Verify
with the endpoint's RSA public key (the public_key PEM from the webhook API
response). Use the raw request body — don't JSON.parse first.
Quirk: Bridge SHA256-hashes
<timestamp>.<rawBody>to a digest, then RSA-SHA256 verifies that digest — so the digest is hashed again insideverify. Feed the digest (not the raw string) into an RSA-SHA256 verifier, exactly as below.
const crypto = require('crypto');
function verifyBridgeSignature(rawBody, header, publicKeyPem, toleranceMs = 10 * 60 * 1000) {
const parts = {}; // split on FIRST '=' — base64 '=' padding is safe
for (const p of header.split(',')) {
const i = p.indexOf('=');
parts[p.slice(0, i)] = p.slice(i + 1);
}
const { t: timestamp, v0: signature } = parts;
if (!timestamp || !signature) return false;
if (Date.now() - Number(timestamp) > toleranceMs) return false; // reject stale events (replay guard)
const digest = crypto.createHash('sha256').update(`${timestamp}.${rawBody}`).digest();
const verifier = crypto.createVerify('sha256'); // RSA-SHA256 hashes `digest` a second time
verifier.update(digest);
verifier.end();
try {
return verifier.verify(publicKeyPem, 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 398 B
- examples/express/package.json 385 B
- examples/express/README.md 1.3 KB
- examples/express/src/index.js 4.9 KB runs code
- examples/express/test/webhook.test.js 5.2 KB runs code
- examples/fastapi/.env.example 337 B
- examples/fastapi/main.py 4.6 KB runs code
- examples/fastapi/README.md 1.5 KB
- examples/fastapi/requirements.txt 103 B
- examples/fastapi/test_webhook.py 5.2 KB runs code
- examples/nextjs/.env.example 339 B
- examples/nextjs/app/webhooks/bridge-xyz/route.ts 4.1 KB runs code
- examples/nextjs/package.json 497 B
- examples/nextjs/README.md 1.4 KB
- examples/nextjs/test/webhook.test.ts 4.4 KB runs code
- examples/nextjs/vitest.config.ts 140 B runs code
- references/overview.md 4.0 KB
- references/setup.md 3.8 KB
- references/verification.md 6.7 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.
- 6d ago First seen · 140 lines · 64 tokens per session scan A 9db58f5ef8ab
bridge-xyz-webhooks is a skill published in the GitHub repository hookdeck/webhook-skills (84 stars, last pushed 2d ago), licensed MIT. It adds 64 tokens to every session and 1,732 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.
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…