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 fireblocks-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/fireblocks-webhooks)<a href="https://agentmods.dev/skills/hookdeck/webhook-skills/fireblocks-webhooks"><img src="https://agentmods.dev/badge/skills/hookdeck/webhook-skills/fireblocks-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/fireblocks-webhooks"><img src="https://agentmods.dev/badge/skills/hookdeck/webhook-skills/fireblocks-webhooks.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 85 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00065 | $0.01600 |
| Opus 5.5 | $0.00026 | $0.00640 |
| Sonnet 5.5 | $0.00013 | $0.00320 |
| Haiku 4.5 | $0.00006 | $0.00160 |
Grade A, and why
fireblocks-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.
How it starts
The opening of the file, as written. The whole thing — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fireblocks Webhooks
When to Use This Skill
- How do I receive Fireblocks webhooks?
- How do I verify the
Fireblocks-Webhook-Signatureheader? - Why is my Fireblocks webhook signature verification failing?
- How do I handle
transaction.createdortransaction.status.updatedevents? - How do I validate a Fireblocks detached JWS (RS512) against the JWKS endpoint?
Verification (core)
Fireblocks Webhooks v2 signs every request with a detached JWS (RS512, RSA + SHA-512) in the Fireblocks-Webhook-Signature header. The header is a compact JWS with an empty payload segment (<protected-header>..<signature>). To verify, reinsert the raw request body (base64url-encoded) as the payload, then verify against the auto-rotated regional JWKS (https://keys.fireblocks.io/.well-known/jwks.json). Use the raw body bytes — never JSON.parse first.
import { createRemoteJWKSet, compactVerify } from 'jose';
const JWKS = createRemoteJWKSet(
new URL('https://keys.fireblocks.io/.well-known/jwks.json')
);
// signatureHeader = value of the `Fireblocks-Webhook-Signature` header (detached JWS)
export async function verifyFireblocksWebhook(rawBody, signatureHeader) {
const [header, , signature] = signatureHeader.split('.'); // header .. signature
const payload = Buffer.from(rawBody).toString('base64url'); // raw body as JWS payload
const fullJws = `${header}.${payload}.${signature}`;
const { payload: verified } = await compactVerify(fullJws, JWKS, {
algorithms: ['RS512'], // pin alg (no alg confusion)
});
return JSON.parse(Buffer.from(verified).toString('utf8')); // { id, eventType, data, ... }
}
For complete handlers with route wiring, event dispatch, and tests, see:
Legacy (Webhooks v1): the older
Fireblocks-Signatureheader (base64 RSA PKCS#1 v1.5 over the SHA-512 hash of the raw body, verified against a static per-environment PEM key) reached its migration deadline on March 20, 2026. New integrations should use the v2 JWKS scheme above. See references/verification.md for the legacy path.
What ships with it
22 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 331 B
- examples/express/package.json 426 B
- examples/express/README.md 1.6 KB
- examples/express/src/index.js 2.7 KB runs code
- examples/express/src/verify.js 2.3 KB runs code
- examples/express/test/webhook.test.js 4.7 KB runs code
- examples/fastapi/.env.example 331 B
- examples/fastapi/main.py 4.4 KB runs code
- examples/fastapi/README.md 2.0 KB
- examples/fastapi/requirements.txt 364 B
- examples/fastapi/test_webhook.py 4.4 KB runs code
- examples/nextjs/.env.example 291 B
- examples/nextjs/app/webhooks/fireblocks/route.ts 1.9 KB runs code
- examples/nextjs/lib/verify.ts 2.2 KB runs code
- examples/nextjs/package.json 479 B
- examples/nextjs/README.md 1.8 KB
- examples/nextjs/test/webhook.test.ts 3.7 KB runs code
- examples/nextjs/tsconfig.json 585 B
- examples/nextjs/vitest.config.ts 157 B runs code
- references/overview.md 3.6 KB
- references/setup.md 3.5 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.
- 1mo ago First seen · 119 lines · 65 tokens per session scan A 8d99994e2caa
fireblocks-webhooks is a skill published in the GitHub repository hookdeck/webhook-skills (92 stars, last pushed yesterday), licensed MIT. It adds 65 tokens to every session and 1,600 once invoked, about $0.0003 per session on Opus 5.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
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…