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/ascend-webhooksnpx skills add hookdeck/webhook-skills --skill ascend-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.00061 | $0.01837 |
| Opus 5 | $0.00030 | $0.00919 |
| Sonnet 5 | $0.00012 | $0.00367 |
| Haiku 4.5 | $0.00006 | $0.00184 |
Grade A, and why
ascend-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 — 173 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ascend Webhooks
Ascend (insurance payments / premium financing) sends webhooks so your app is notified when an event happens — for example when an invoice is paid. Ascend POSTs a JSON payload over HTTPS and signs it with an HMAC-SHA256 signature you must verify before trusting the event.
When to Use This Skill
- How do I receive Ascend webhooks?
- How do I verify Ascend webhook signatures?
- How do I parse the
X-Ascend-Signatureheader? - How do I handle
invoice.paid(or payout / refund) events? - Why is my Ascend webhook signature verification failing?
How Ascend Signs Webhooks
Ascend uses a custom Stripe-style HMAC-SHA256 scheme (not Svix, not Standard Webhooks). Two headers are sent:
| Header | Example | Purpose |
|---|---|---|
X-Ascend-Signature |
t=1696200697,v1=5257a869e7... |
Timestamp + HMAC signature |
X-Ascend-Request-Timestamp |
1696200697 |
Same Unix timestamp (redundant) |
The signature is verified by:
- Parse
X-Ascend-Signatureintot(timestamp) andv1(hex HMAC). - Build the signed string as
`${t}:${rawBody}`— the timestamp, a colon, then the raw request body. - Compute
HMAC-SHA256(signed_string, webhook_secret)and hex-encode it. - Constant-time compare against
v1.
Use the raw request body. Re-serializing the parsed JSON (key reordering, whitespace) changes the bytes and breaks the signature. There is no official Ascend SDK, so every framework below verifies manually.
Verification (core)
const crypto = require('crypto');
// Verify Ascend's "t=<timestamp>,v1=<hex>" signature over "<timestamp>:<rawBody>".
function verifyAscendSignature(rawBody, signatureHeader, secret) {
const parts = Object.fromEntries(
signatureHeader.split(',').map((p) => p.split('=').map((s) => s.trim()))
);
const { t: timestamp, v1: signature } = parts;
if (!timestamp || !signature) return false;
const expected = crypto
.createHmac('sha256', secret)
.update(`${timestamp}:${rawBody}`) // colon separator + RAW body
.digest('hex');
try {
return crypto.timingSafeEqual(
Buffer.from(signature, 'hex'),
Buffer.from(expected, 'hex')
);
} 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 201 B
- examples/express/package.json 368 B
- examples/express/README.md 1.6 KB
- examples/express/src/index.js 3.2 KB runs code
- examples/express/test/webhook.test.js 3.9 KB runs code
- examples/fastapi/.env.example 131 B
- examples/fastapi/main.py 2.8 KB runs code
- examples/fastapi/README.md 1.6 KB
- examples/fastapi/requirements.txt 82 B
- examples/fastapi/test_webhook.py 4.1 KB runs code
- examples/nextjs/.env.example 131 B
- examples/nextjs/app/webhooks/ascend/route.ts 2.8 KB runs code
- examples/nextjs/package.json 480 B
- examples/nextjs/README.md 1.6 KB
- examples/nextjs/test/webhook.test.ts 3.5 KB runs code
- examples/nextjs/vitest.config.ts 140 B runs code
- references/overview.md 4.2 KB
- references/setup.md 2.6 KB
- references/verification.md 4.7 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 · 173 lines · 61 tokens per session scan A 4e0555d70a08
ascend-webhooks is a skill published in the GitHub repository hookdeck/webhook-skills (84 stars, last pushed 6d ago), licensed MIT. It adds 61 tokens to every session and 1,837 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.