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/twitter-webhooksnpx skills add hookdeck/webhook-skills --skill twitter-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/twitter-webhooks)<a href="https://agentmods.dev/skills/hookdeck/webhook-skills/twitter-webhooks"><img src="https://agentmods.dev/badge/skills/hookdeck/webhook-skills/twitter-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.00073 | $0.01892 |
| Opus 5 | $0.00036 | $0.00946 |
| Sonnet 5 | $0.00015 | $0.00378 |
| Haiku 4.5 | $0.00007 | $0.00189 |
Grade A, and why
twitter-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 — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Twitter / X Webhooks
Twitter/X delivers account activity through the Account Activity API. Your public HTTPS endpoint must do two things:
- Answer the CRC (Challenge-Response Check) — X sends a
GETrequest with acrc_tokenquery parameter at registration, roughly hourly, and on demand. You must reply within the timeout with aresponse_token, or the webhook is marked invalid and delivery stops. - Verify POST deliveries — every event
POSTcarries anx-twitter-webhooks-signatureheader you validate before processing.
Both use the same primitive: HMAC-SHA256 keyed with your app's consumer
secret (API secret key), base64-encoded, prefixed with sha256=. Use the
consumer secret — not the bearer token or user access token.
When to Use This Skill
- How do I receive Twitter/X (Account Activity API) webhooks?
- How do I verify the
x-twitter-webhooks-signatureheader? - How do I respond to the X CRC /
crc_tokenchallenge? - How do I handle
tweet_create_events,follow_events, ordirect_message_events? - Why is my X webhook being marked invalid / why did delivery stop?
Verification (core)
X signs the raw request body (for POST events) or the crc_token value
(for the CRC GET) with HMAC-SHA256 using the consumer secret, base64-encodes it,
and prepends sha256=. The exact same helper produces both values:
const crypto = require('crypto');
// sha256= + base64(HMAC-SHA256(consumerSecret, message))
function buildSignature(message, consumerSecret) {
return 'sha256=' + crypto
.createHmac('sha256', consumerSecret)
.update(message)
.digest('base64');
}
// CRC GET: reply { response_token: buildSignature(crc_token, secret) }
// POST: compare buildSignature(rawBody, secret) to the header, timing-safe
function verifyTwitterSignature(rawBody, signatureHeader, consumerSecret) {
if (!signatureHeader || !consumerSecret) return false;
const expected = buildSignature(rawBody, consumerSecret);
try {
return crypto.timingSafeEqual(Buffer.from(signatureHeader), Buffer.from(expected));
} catch {
return false; // length mismatch = invalid
}
}
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 166 B
- examples/express/package.json 393 B
- examples/express/README.md 1.2 KB
- examples/express/src/index.js 5.4 KB runs code
- examples/express/test/webhook.test.js 5.3 KB runs code
- examples/fastapi/.env.example 166 B
- examples/fastapi/main.py 4.8 KB runs code
- examples/fastapi/README.md 1.4 KB
- examples/fastapi/requirements.txt 82 B
- examples/fastapi/test_webhook.py 6.0 KB runs code
- examples/nextjs/.env.example 166 B
- examples/nextjs/app/webhooks/twitter/route.ts 4.5 KB runs code
- examples/nextjs/package.json 516 B
- examples/nextjs/README.md 1.2 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.5 KB
- references/setup.md 3.0 KB
- references/verification.md 4.1 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 · 157 lines · 73 tokens per session scan A fa962ad51824
twitter-webhooks is a skill published in the GitHub repository hookdeck/webhook-skills (84 stars, last pushed 2d ago), licensed MIT. It adds 73 tokens to every session and 1,892 once invoked, about $0.0004 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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
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…