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/aiprise-webhooksnpx skills add hookdeck/webhook-skills --skill aiprise-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/aiprise-webhooks)<a href="https://agentmods.dev/skills/hookdeck/webhook-skills/aiprise-webhooks"><img src="https://agentmods.dev/badge/skills/hookdeck/webhook-skills/aiprise-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.00059 | $0.01418 |
| Opus 5 | $0.00030 | $0.00709 |
| Sonnet 5 | $0.00012 | $0.00284 |
| Haiku 4.5 | $0.00006 | $0.00142 |
Grade A, and why
aiprise-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 5d 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.
This is a copy
75% identical to adyen-webhooks — 169 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AiPrise Webhooks
AiPrise is an identity verification (KYC/KYB) platform. It notifies your server of verification outcomes and business-profile changes via callbacks — signed HTTP POST webhooks.
When to Use This Skill
- How do I receive AiPrise webhooks (callbacks)?
- How do I verify the AiPrise
X-HMAC-SIGNATUREheader? - How do I handle
APPROVED,DECLINED,REVIEW, orUNKNOWNverification results? - Why is my AiPrise webhook signature verification failing?
- How do I correlate a callback with a verification session?
Verification (core)
AiPrise signs every callback with HMAC-SHA256 over the raw request body,
lowercase hex, in the X-HMAC-SIGNATURE header. The HMAC key is your AiPrise API
private key directly (e.g. abcdef12-pqrs-...) — there is no separate signing or
endpoint secret, and this is not Standard Webhooks. Verify against the exact raw
body bytes; re-serializing the JSON changes bytes and breaks the signature.
const crypto = require('crypto');
function verifyAiPriseWebhook(rawBody, signatureHeader, apiKey) {
if (!signatureHeader) return false;
const expected = crypto
.createHmac('sha256', apiKey)
.update(rawBody) // Buffer/string of the raw HTTP body — do NOT JSON.parse first
.digest('hex')
.toLowerCase();
try {
return crypto.timingSafeEqual(
Buffer.from(signatureHeader.toLowerCase(), 'hex'),
Buffer.from(expected, 'hex')
);
} catch {
return false; // length mismatch / malformed hex
}
}
For complete handlers with route wiring, event dispatch, and tests, see:
Verification Results
There is no rich typed-event system — the outcome is the
aiprise_summary.verification_result value:
verification_result |
Meaning | Typical action |
|---|---|---|
APPROVED |
Verification passed | Provision access / mark verified |
DECLINED |
Verification failed | Block / request resubmission |
REVIEW |
Needs manual review | Queue for an analyst |
UNKNOWN |
Result indeterminate | Retry / investigate |
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 177 B
- examples/express/package.json 381 B
- examples/express/README.md 989 B
- examples/express/src/index.js 3.5 KB runs code
- examples/express/test/webhook.test.js 4.6 KB runs code
- examples/fastapi/.env.example 177 B
- examples/fastapi/main.py 2.7 KB runs code
- examples/fastapi/README.md 1.2 KB
- examples/fastapi/requirements.txt 82 B
- examples/fastapi/test_webhook.py 4.8 KB runs code
- examples/nextjs/.env.example 177 B
- examples/nextjs/app/webhooks/aiprise/route.ts 2.7 KB runs code
- examples/nextjs/package.json 494 B
- examples/nextjs/README.md 1.0 KB
- examples/nextjs/test/webhook.test.ts 3.6 KB runs code
- examples/nextjs/vitest.config.ts 140 B runs code
- references/overview.md 3.4 KB
- references/setup.md 2.5 KB
- references/verification.md 5.3 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.
- 5d ago First seen · 130 lines · 59 tokens per session scan A a6584ffd6517
aiprise-webhooks is a skill published in the GitHub repository hookdeck/webhook-skills (84 stars, last pushed yesterday), licensed MIT. It adds 59 tokens to every session and 1,418 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 75% identical to adyen-webhooks, differing in 169 lines, and is treated as a copy.
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…