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/airtable-webhooksnpx skills add hookdeck/webhook-skills --skill airtable-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.00065 | $0.01793 |
| Opus 5 | $0.00032 | $0.00897 |
| Sonnet 5 | $0.00013 | $0.00359 |
| Haiku 4.5 | $0.00006 | $0.00179 |
Grade A, and why
airtable-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 2d 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 — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Airtable Webhooks
When to Use This Skill
- Setting up Airtable webhook handlers
- How do I verify the
X-Airtable-Content-MACsignature? - Why is my Airtable webhook signature verification failing?
- How do I fetch the actual changes after an Airtable notification?
- Handling base changes:
tableData,tableFields,tableMetadatawithadd/remove/update
The Thin-Ping Model (Read This First)
Airtable webhooks are a two-step, thin-ping design and do not follow the Standard Webhooks spec:
-
Notification POST — Airtable POSTs a tiny body to your
notificationUrlcontaining only which base/webhook changed and a timestamp. No change data.{ "base": { "id": "appABC" }, "webhook": { "id": "achXYZ" }, "timestamp": "2022-02-01T21:25:05.663Z" }You must respond 200 or 204 with an empty body within 25 seconds.
-
Fetch payloads — To get the actual changes, call
GET /v0/bases/{baseId}/webhooks/{webhookId}/payloadswith a persisted cursor (a monotonically increasing transaction number). The response returnspayloads, the nextcursor, andmightHaveMore(loop while true; maxlimitis 50).
Verification (core)
Airtable signs the raw notification body with HMAC-SHA256, keyed on the
base64-decoded macSecretBase64 returned once at webhook creation. The digest
is hex and the header value is prefixed with hmac-sha256=.
Node:
const crypto = require('crypto');
function verify(rawBody, macHeader, macSecretBase64) {
if (!macHeader) return false;
const key = Buffer.from(macSecretBase64, 'base64');
const expected = 'hmac-sha256=' + crypto.createHmac('sha256', key).update(rawBody).digest('hex');
try {
return crypto.timingSafeEqual(Buffer.from(macHeader), Buffer.from(expected));
} catch {
return false; // length mismatch = invalid
}
}
Python:
import hmac, hashlib, base64
def verify(raw_body: bytes, mac_header: str, mac_secret_base64: str) -> bool:
if not mac_header:
return False
key = base64.b64decode(mac_secret_base64)
expected = "hmac-sha256=" + hmac.new(key, raw_body, hashlib.sha256).hexdigest()
return hmac.compare_digest(mac_header, expected)
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 395 B
- examples/express/package.json 372 B
- examples/express/README.md 1.7 KB
- examples/express/src/index.js 5.6 KB runs code
- examples/express/test/webhook.test.js 4.1 KB runs code
- examples/fastapi/.env.example 335 B
- examples/fastapi/main.py 4.4 KB runs code
- examples/fastapi/README.md 1.5 KB
- examples/fastapi/requirements.txt 82 B
- examples/fastapi/test_webhook.py 4.2 KB runs code
- examples/nextjs/.env.example 335 B
- examples/nextjs/app/webhooks/airtable/route.ts 4.3 KB runs code
- examples/nextjs/package.json 484 B
- examples/nextjs/README.md 1.4 KB
- examples/nextjs/test/webhook.test.ts 3.5 KB runs code
- examples/nextjs/vitest.config.ts 140 B runs code
- references/overview.md 3.1 KB
- references/setup.md 3.2 KB
- references/verification.md 3.6 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.
- 2d ago First seen · 156 lines · 65 tokens per session scan A 8eac2b53c883
airtable-webhooks is a skill published in the GitHub repository hookdeck/webhook-skills (84 stars, last pushed 6d ago), licensed MIT. It adds 65 tokens to every session and 1,793 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.