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/community-webhooksnpx skills add hookdeck/webhook-skills --skill community-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.00060 | $0.02337 |
| Opus 5 | $0.00030 | $0.01169 |
| Sonnet 5 | $0.00012 | $0.00467 |
| Haiku 4.5 | $0.00006 | $0.00234 |
Grade A, and why
community-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 3d 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 — 205 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Community Webhooks
Webhooks from Community (community.com) — the SMS / conversational-messaging platform for brands and creators. This is not a generic community-forum product, not Circle/Discourse/Bettermode, and not Salesforce Experience Cloud. The developer hub is https://developer.community.com.
When to Use This Skill
- How do I receive Community webhooks?
- How do I verify the
community-signatureheader? - Why is my Community webhook signature verification failing?
- How do I handle
message.inbound/message.outboundevents? - How do I handle
member.created,member.updated, andmember.deletedevents? - How do I deduplicate Community webhooks (at-least-once delivery)?
Verification (core)
Community signs every request with HMAC-SHA256 over {timestamp}.{raw_body}
and sends the result in a Stripe-style community-signature header:
community-signature: t=1711666033,v1=b777f6ae2497ae95e99811c88b28d8ba377c95d615905963c68fae4c800de48d
The HMAC key is the signature secret, which is unique to each webhook
(Dashboard → Settings → Integrations → Webhooks). It is not your
community_api-prefixed Async REST API token. Always HMAC the raw request
body — re-serializing the JSON changes the bytes and breaks the signature.
const crypto = require('crypto');
function verifyCommunitySignature(rawBody, signatureHeader, secret) {
if (!signatureHeader || !secret) return false;
// Parse "t=...,v1=..." without assuming field order
const fields = Object.fromEntries(
signatureHeader.split(',').map((p) => {
const i = p.indexOf('=');
return i === -1 ? ['', ''] : [p.slice(0, i).trim(), p.slice(i + 1).trim()];
})
);
const timestamp = fields.t;
const signature = fields.v1; // only the v1 scheme is supported
if (!timestamp || !signature) return false;
// Signed content is: timestamp + "." + raw body
const expected = crypto
.createHmac('sha256', secret)
.update(`${timestamp}.${rawBody}`, 'utf8')
.digest('hex');
try {
return crypto.timingSafeEqual(Buffer.from(signature), Buffer.from(expected));
} catch {
return false; // length mismatch
}
}
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 603 B
- examples/express/package.json 390 B
- examples/express/README.md 2.6 KB
- examples/express/src/index.js 7.4 KB runs code
- examples/express/test/webhook.test.js 12 KB runs code
- examples/fastapi/.env.example 555 B
- examples/fastapi/main.py 7.3 KB runs code
- examples/fastapi/README.md 3.0 KB
- examples/fastapi/requirements.txt 82 B
- examples/fastapi/test_webhook.py 12 KB runs code
- examples/nextjs/.env.example 555 B
- examples/nextjs/app/webhooks/community/route.ts 6.5 KB runs code
- examples/nextjs/package.json 512 B
- examples/nextjs/README.md 2.7 KB
- examples/nextjs/test/webhook.test.ts 12 KB runs code
- examples/nextjs/vitest.config.ts 140 B runs code
- references/overview.md 8.1 KB
- references/setup.md 4.3 KB
- references/verification.md 9.8 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.
- 3d ago First seen · 205 lines · 60 tokens per session scan A e12d70ca73c9
community-webhooks is a skill published in the GitHub repository hookdeck/webhook-skills (84 stars, last pushed 6d ago), licensed MIT. It adds 60 tokens to every session and 2,337 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
wiki
Rebuild a flow-first project wiki using the mimirs wiki MCP tool. Use when the user asks to generate, rebuild, refresh, or write the wiki for a codebase.
scout
Research the web for solutions, competitors, alternatives, or prior art for a decision facing this project — then store the findings in project memory so they survive the session. Use when choosing a library or approach, comparing tools, checking what others do, or evaluating whether to build vs adopt.
plan
Design an implementation plan before writing code — where the change lands, what it will touch, what could break, and the steps in order. Use when asked to plan a feature, scope a change, or figure out how to approach an edit before making it. To assess a change that already exists (a diff, refactor, or rename), use…
research
Answer a hard, open-ended question about how the project works or is built by synthesizing every source — code, structure, git history, prior decisions, discussion, caveats — and verifying each claim against the source. Use for deep cross-cutting questions that span more than one area. Narrower siblings — a single…
explore
Build an accurate mental model of an unfamiliar codebase, feature, or area before changing it — where it lives, how it connects, what it does, and why. Use when asked how something works, where something is, when onboarding to a repo, or before editing code you don't know. For a cross-cutting question that needs…
handoff
Wrap up a work session so the next session (or another agent) can pick up cleanly — what was done, what's in flight, what to watch out for. Use when ending a session, switching tasks, or asked to hand off, wrap up, or save state for later.