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/statsig-webhooksnpx skills add hookdeck/webhook-skills --skill statsig-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/statsig-webhooks)<a href="https://agentmods.dev/skills/hookdeck/webhook-skills/statsig-webhooks"><img src="https://agentmods.dev/badge/skills/hookdeck/webhook-skills/statsig-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 | $0.00053 | $0.02494 |
| Opus 5 | $0.00026 | $0.01247 |
| Sonnet 5 | $0.00011 | $0.00499 |
| Haiku 4.5 | $0.00005 | $0.00249 |
Grade A, and why
statsig-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 yesterday.
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 — 245 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Statsig Webhooks
When to Use This Skill
- Setting up a Statsig Event Webhook (the "Generic Webhook" integration)
- Debugging
X-Statsig-Signatureverification failures - Processing exposure events or config-change notifications (feature gate,
experiment, or dynamic config
created/updatedevents) - Handling Statsig's JSON batch payloads (arrays) and the config-change
{ "data": [...] }envelope - Answering the
url_verificationhandshake so the webhook actually registers (a missed handshake fails silently — no events, no log entries)
Essential Code (USE THIS)
Statsig signs every webhook request with HMAC-SHA256 using a Slack/Stripe-style
scheme (this is not the Standard Webhooks spec). The signed content is the
literal string v0:{timestamp}:{raw_body}, and the result is sent as
X-Statsig-Signature: v0=<hex>. Use the raw request body — parsing JSON
before verifying will change byte ordering and break the signature.
Note: Statsig's
X-Statsig-Request-Timestampis a Unix timestamp in milliseconds (13 digits), not seconds.
URL Validation Handshake (answer this or the webhook never registers)
When you save the Generic Webhook integration, Statsig POSTs a validation request to the destination URL and registers the webhook only if the endpoint echoes the code back:
{ "data": { "event": "url_verification", "verification_code": "abc123" } }
Respond 200 with a JSON body carrying the same value:
{ "verification_code": "abc123" }
A missed handshake fails silently: the webhook never registers, no event is ever delivered, and nothing appears in any delivery log. Answer it before enforcing signature verification — it only echoes a value the caller supplied, the same way an unauthenticated URL-check ping is answered for providers like Mailchimp. The Express handler below includes the responder.
Statsig Signature Verification (JavaScript)
const crypto = require('crypto');
function verifyStatsigRequest(rawBody, signatureHeader, timestampHeader, signingSecret) {
if (!signatureHeader || !timestampHeader || !signingSecret) return false;
// Statsig's timestamp is a Unix time in MILLISECONDS (13 digits)
const timestamp = parseInt(timestampHeader, 10);
if (Number.isNaN(timestamp)) return false;
// Replay protection (best practice; Statsig does not document a tolerance):
// reject requests whose timestamp is more than 5 minutes from now.
if (Math.abs(Date.now() - timestamp) > 5 * 60 * 1000) return false;
// Statsig signs the literal string: "v0:" + timestamp + ":" + raw body
const basestring = `v0:${timestampHeader}:${rawBody}`;
const expected = 'v0=' + crypto
.createHmac('sha256', signingSecret)
.update(basestring, 'utf8')
.digest('hex');
try {
return crypto.timingSafeEqual(
Buffer.from(signatureHeader),
Buffer.from(expected)
);
} 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 190 B
- examples/express/package.json 376 B
- examples/express/README.md 1.3 KB
- examples/express/src/index.js 4.1 KB runs code
- examples/express/test/webhook.test.js 6.4 KB runs code
- examples/fastapi/.env.example 190 B
- examples/fastapi/main.py 3.8 KB runs code
- examples/fastapi/README.md 1.3 KB
- examples/fastapi/requirements.txt 82 B
- examples/fastapi/test_webhook.py 6.7 KB runs code
- examples/nextjs/.env.example 190 B
- examples/nextjs/app/webhooks/statsig/route.ts 3.3 KB runs code
- examples/nextjs/package.json 497 B
- examples/nextjs/README.md 1.1 KB
- examples/nextjs/test/webhook.test.ts 4.6 KB runs code
- examples/nextjs/vitest.config.ts 140 B runs code
- references/overview.md 3.2 KB
- references/setup.md 2.4 KB
- references/verification.md 6.0 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.
- yesterday First seen · 245 lines · 53 tokens per session scan A 0dd167a2ccfa
statsig-webhooks is a skill published in the GitHub repository hookdeck/webhook-skills (84 stars, last pushed yesterday), licensed MIT. It adds 53 tokens to every session and 2,494 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-09-03.
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…