fanvue-webhooks

fanvue-webhooks is a skill for Claude Code, Codex from hookdeck/webhook-skills. It costs 98 tokens per session (2,883 once invoked), scanned A, a copy of adyen-webhooks, MIT.

A guide for receiving and checking Fanvue webhooks, which are HTTP messages sent by Fanvue when events happen in an account. It covers signed messages and Fanvue event handling.

In plain words
What is it for?
Use it when building a Fanvue webhook endpoint, checking signed requests, answering the verification probe, or handling payment, subscription, message, checkout, and payout events.
Why use it?
It helps prevent untrusted requests from being accepted and explains issues with signature checking, secret changes, and Fanvue's initial verification request.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it when building a Fanvue webhook endpoint, checking signed requests, answering the verification probe, or handling payment, subscription, message, checkout, and payout events.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/hookdeck/webhook-skills/fanvue-webhooks
Install

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.

Any agent
npx skills add hookdeck/webhook-skills --skill fanvue-webhooks
Clone the repo
git clone --depth 1 https://github.com/hookdeck/webhook-skills

Made for: Claude Code, Codex.

Its marketplace also offers this one on its own, as the plugin fanvue-webhooks — /plugin install fanvue-webhooks after adding the marketplace above.

Wrote 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.

agentmods badge for fanvue-webhooks

README.md
[![agentmods](https://agentmods.dev/badge/skills/hookdeck/webhook-skills/fanvue-webhooks/github.svg)](https://agentmods.dev/skills/hookdeck/webhook-skills/fanvue-webhooks)
Your own site
<a href="https://agentmods.dev/skills/hookdeck/webhook-skills/fanvue-webhooks"><img src="https://agentmods.dev/badge/skills/hookdeck/webhook-skills/fanvue-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.

agentmods 80×15 button for fanvue-webhooks

Your own site · 80×15
<a href="https://agentmods.dev/skills/hookdeck/webhook-skills/fanvue-webhooks"><img src="https://agentmods.dev/badge/skills/hookdeck/webhook-skills/fanvue-webhooks.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 98 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,883 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 80% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00098 $0.02883
Opus 5.5 $0.00039 $0.01153
Sonnet 5.5 $0.00020 $0.00577
Haiku 4.5 $0.00010 $0.00288

Measured today against content hash 1036108834ef, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

fanvue-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 today.

The scan reads SKILL.md. This mod also ships 8 executable files (examples/express/src/index.js, examples/express/test/webhook.test.js, examples/fastapi/main.py, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

Origin

This is a copy

80% identical to adyen-webhooks — 292 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.

skills/fanvue-webhooks/SKILL.md · 273 lines

How it starts

The opening of the file, as written. The whole thing — 273 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Fanvue Webhooks

When to Use This Skill

  • Setting up a Fanvue webhook endpoint for a Developer Area app
  • Verifying the X-Fanvue-Signature header (or debugging why it fails)
  • Why does POST /webhooks/subscriptions fail against my endpoint? (the unsigned probe)
  • Handling creator, checkout link, payout or app billing events
  • Migrating from legacy flat events (purchase.new, tip.new, subscription.new) to creator.*

Verification (core)

Every delivery carries:

X-Fanvue-Signature: t=<unix seconds>,v0=<hex>
X-Fanvue-Signature: t=<unix seconds>,v0=<old hex>,<new hex>   # during secret rotation

The signature is HMAC-SHA256 over <t>.<raw body>, hex encoded, keyed with the signing secret exactly as Fanvue gives it (don't strip whsec_). The rotation MAC arrives as a bare field with no =, so parse the header statefully and accept when any MAC matches. Reject t more than 300 seconds from now, and respond 401 on failure.

Node (from examples/express/):

function parseSignatureHeader(header) {
  let key;
  let timestamp;
  let timestampCount = 0;
  const macs = [];

  for (const field of header.split(',')) {
    const separator = field.indexOf('=');
    if (separator !== -1) key = field.slice(0, separator).trim();
    // With separator === -1 this is the whole bare field.
    const value = field.slice(separator + 1).trim();
    if (key === 't') {
      timestamp = value;
      timestampCount += 1;
    } else if (key === 'v0' && value) {
      macs.push(value.toLowerCase());
    }
  }

  return { timestamp, timestampCount, macs };
}

function verifyFanvueSignature(
  rawBody,
  header,
  secret,
  toleranceSeconds = TOLERANCE_SECONDS,
  nowSeconds = Math.floor(Date.now() / 1000)
) {
  if (!header) {
    return { valid: false, error: 'Missing X-Fanvue-Signature header' };
  }

  const { timestamp, timestampCount, macs } = parseSignatureHeader(header);
  if (timestampCount !== 1 || !/^[0-9]+$/.test(timestamp) || macs.length === 0) {
    return { valid: false, error: 'Malformed X-Fanvue-Signature header' };
  }

  // `t` is inside the signed content, so it can't be refreshed on a replay.
  if (Math.abs(nowSeconds - Number(timestamp)) > toleranceSeconds) {
    return { valid: false, error: 'Timestamp outside tolerance' };
  }

  const expected = crypto
    .createHmac('sha256', secret)
    .update(`${timestamp}.`)
    .update(rawBody)
    .digest('hex');

  // Accept when ANY MAC matches (two MACs are sent during secret rotation).
  const matched = macs.some(
    (mac) =>
      mac.length === expected.length &&
      crypto.timingSafeEqual(Buffer.from(mac), Buffer.from(expected))
  );

  return matched ? { valid: true } : { valid: false, error: 'Invalid signature' };
}

Read the full file on GitHub · 273 lines

Changes

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.

  1. today First seen · 273 lines · 98 tokens per session scan A 1036108834ef

Subscribe to this mod's changes

fanvue-webhooks is a skill published in the GitHub repository hookdeck/webhook-skills (92 stars, last pushed yesterday), licensed MIT. It adds 98 tokens to every session and 2,883 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 80% identical to adyen-webhooks, differing in 292 lines, and is treated as a copy.

Related

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…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

vercel/next.js · 95 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens

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…

vercel/next.js · 83 tokens