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/enode-webhooksnpx skills add hookdeck/webhook-skills --skill enode-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.00052 | $0.01524 |
| Opus 5 | $0.00026 | $0.00762 |
| Sonnet 5 | $0.00010 | $0.00305 |
| Haiku 4.5 | $0.00005 | $0.00152 |
Grade A, and why
enode-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 — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Enode Webhooks
When to Use This Skill
- Setting up Enode webhook handlers
- Debugging Enode signature verification failures
- Understanding Enode event types and payloads
- Handling
user:vehicle:updated,user:charger:updated, oruser:battery:updatedevents - Why is my Enode webhook signature verification (
x-enode-signature) failing?
Verification (core)
Enode signs the raw request body with HMAC-SHA1 keyed on the per-webhook secret you generated (min 128 bits) and supplied at webhook creation. The digest is sent in the x-enode-signature header formatted as sha1=<hex> (lowercase hex). Enode does not follow the Standard Webhooks spec. Pass the raw body, and compare timing-safe.
Node:
const crypto = require('crypto');
function verify(rawBody, signatureHeader, secret) {
const [algo, sig] = (signatureHeader || '').split('=');
if (algo !== 'sha1' || !sig) return false;
const expected = crypto.createHmac('sha1', secret).update(rawBody).digest('hex');
try {
return crypto.timingSafeEqual(Buffer.from(sig), Buffer.from(expected));
} catch {
return false;
}
}
Python:
import hmac, hashlib
def verify(raw_body: bytes, signature_header: str, secret: str) -> bool:
algo, _, sig = (signature_header or "").partition("=")
if algo != "sha1" or not sig:
return False
expected = hmac.new(secret.encode(), raw_body, hashlib.sha1).hexdigest()
return hmac.compare_digest(sig, expected)
For complete handlers with route wiring, event dispatch, and tests, see:
Payload Shape
The webhook body is a JSON array of events — a single delivery can carry multiple events. Iterate the array; each element has an event name, a createdAt timestamp, and a version:
[
{ "event": "user:vehicle:updated", "createdAt": "2020-04-07T17:04:26Z", "version": "..." }
]
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 129 B
- examples/express/package.json 366 B
- examples/express/README.md 1014 B
- examples/express/src/index.js 4.2 KB runs code
- examples/express/test/webhook.test.js 5.4 KB runs code
- examples/fastapi/.env.example 129 B
- examples/fastapi/main.py 3.8 KB runs code
- examples/fastapi/README.md 1.0 KB
- examples/fastapi/requirements.txt 82 B
- examples/fastapi/test_webhook.py 6.0 KB runs code
- examples/nextjs/.env.example 129 B
- examples/nextjs/app/webhooks/enode/route.ts 3.6 KB runs code
- examples/nextjs/package.json 478 B
- examples/nextjs/README.md 870 B
- examples/nextjs/test/webhook.test.ts 3.8 KB runs code
- examples/nextjs/vitest.config.ts 140 B runs code
- references/overview.md 3.6 KB
- references/setup.md 3.5 KB
- references/verification.md 4.5 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 · 141 lines · 52 tokens per session scan A b62121edab09
enode-webhooks is a skill published in the GitHub repository hookdeck/webhook-skills (84 stars, last pushed 5d ago), licensed MIT. It adds 52 tokens to every session and 1,524 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.