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/persona-webhooksnpx skills add hookdeck/webhook-skills --skill persona-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/persona-webhooks)<a href="https://agentmods.dev/skills/hookdeck/webhook-skills/persona-webhooks"><img src="https://agentmods.dev/badge/skills/hookdeck/webhook-skills/persona-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.00051 | $0.01771 |
| Opus 5 | $0.00026 | $0.00886 |
| Sonnet 5 | $0.00010 | $0.00354 |
| Haiku 4.5 | $0.00005 | $0.00177 |
Grade A, and why
persona-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 yesterday.
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 — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Persona Webhooks
When to Use This Skill
- How do I receive Persona webhooks?
- How do I verify the Persona-Signature header?
- Why is my Persona webhook signature verification failing?
- How do I handle inquiry.completed, inquiry.approved, or verification.passed events?
- How do I parse Persona's JSON:API webhook payloads?
Verification (core)
Persona has no official server-side SDK — verify the Persona-Signature
header manually. It is a Stripe-style scheme (NOT Standard Webhooks): the header
is t=<unix_seconds>,v1=<hex>, and v1 is an HMAC-SHA256 hex digest over
`${t}.${rawBody}` keyed with the per-webhook secret (wbhsec_...). Use the
raw request body — never JSON.parse first. During secret rotation the header
carries two space-separated t=...,v1=... pairs; accept if any v1 matches.
const crypto = require('crypto');
function verifyPersonaSignature(rawBody, header, secret) {
if (!header) return false;
// Rotation: header may hold two space-separated "t=...,v1=..." pairs.
return header.trim().split(/\s+/).some((pair) => {
const parts = pair.split(',');
const t = parts.find((p) => p.startsWith('t='))?.slice(2);
const v1 = parts.find((p) => p.startsWith('v1='))?.slice(3);
if (!t || !v1) return false;
const expected = crypto.createHmac('sha256', secret)
.update(`${t}.${rawBody}`).digest('hex');
const a = Buffer.from(v1, 'hex');
const b = Buffer.from(expected, 'hex');
return a.length === b.length && crypto.timingSafeEqual(a, b);
});
}
Persona documents no timestamp tolerance — signature validity is the check. Add your own replay window only if you need one. See references/verification.md for the Python version, rotation details, and gotchas.
For complete handlers with route wiring, event dispatch, and tests, see:
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 169 B
- examples/express/package.json 370 B
- examples/express/README.md 975 B
- examples/express/src/index.js 5.4 KB runs code
- examples/express/test/webhook.test.js 5.9 KB runs code
- examples/fastapi/.env.example 169 B
- examples/fastapi/main.py 4.4 KB runs code
- examples/fastapi/README.md 1.3 KB
- examples/fastapi/requirements.txt 82 B
- examples/fastapi/test_webhook.py 5.9 KB runs code
- examples/nextjs/.env.example 169 B
- examples/nextjs/app/webhooks/persona/route.ts 5.1 KB runs code
- examples/nextjs/package.json 495 B
- examples/nextjs/README.md 1018 B
- examples/nextjs/test/webhook.test.ts 4.8 KB runs code
- examples/nextjs/vitest.config.ts 121 B runs code
- references/overview.md 3.8 KB
- references/setup.md 2.7 KB
- references/verification.md 5.0 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.
- yesterday First seen · 149 lines · 51 tokens per session scan A 1b0c0404ddf2
persona-webhooks is a skill published in the GitHub repository hookdeck/webhook-skills (84 stars, last pushed yesterday), licensed MIT. It adds 51 tokens to every session and 1,771 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-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…
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…
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…