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/praxis-webhooksnpx skills add hookdeck/webhook-skills --skill praxis-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/praxis-webhooks)<a href="https://agentmods.dev/skills/hookdeck/webhook-skills/praxis-webhooks"><img src="https://agentmods.dev/badge/skills/hookdeck/webhook-skills/praxis-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.1 | $0.00073 | $0.02077 |
| Opus 5 | $0.00036 | $0.01038 |
| Sonnet 5 | $0.00015 | $0.00415 |
| Haiku 4.5 | $0.00007 | $0.00208 |
Grade A, and why
praxis-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 — 177 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Praxis Webhooks
Praxis (Praxis Tech, the "Cashier" payment orchestration platform) signs every
outbound webhook with a SHA-384 hex digest in the lowercase
gt-authentication header. This is not an HMAC and not Standard
Webhooks: Praxis takes a fixed, per-webhook-type list of field values in
the documented order, concatenates them into one string, appends your Merchant
Secret, and hashes the result with sha384. Your endpoint must reply 200
with a { "status": 0, ... } body and sign that acknowledgement with the
external-request-signature header.
When to Use This Skill
- How do I receive Praxis / Praxis Tech / Cashier webhooks?
- How do I verify the
gt-authenticationsignature on a Praxis webhook? - Why is my Praxis SHA-384 signature verification failing?
- How do I sign the Praxis acknowledgement (
external-request-signature)? - How do I handle Payment Notification
transaction_status(pending, approved, rejected, error)? - How do I handle a Praxis Subscription Notification
event?
Verification (core)
Concatenate the documented field values in order (do not alphabetize —
that is only for the general API-request signature), append the Merchant Secret,
then sha384 (hex). Compare to the gt-authentication header.
const crypto = require('crypto');
const PAYMENT_FIELDS = ['merchant_id', 'application_key', 'timestamp', 'customer.customer_token',
'session.order_id', 'transaction.tid', 'transaction.currency', 'transaction.amount',
'transaction.conversion_rate', 'transaction.processed_currency', 'transaction.processed_amount'];
const SUBSCRIPTION_FIELDS = ['event', 'merchant_id', 'application_key', 'cid', 'plan_id',
'subscription_id', 'subscription_status', 'timestamp'];
const at = (o, p) => p.split('.').reduce((x, k) => (x == null ? undefined : x[k]), o);
// Subscription Notifications carry an `event` field; Payment Notifications do not.
function verifyPraxis(body, headerSig, merchantSecret) {
const fields = body.event ? SUBSCRIPTION_FIELDS : PAYMENT_FIELDS;
const data = fields.map((p) => String(at(body, p) ?? '')).join('') + merchantSecret;
const expected = crypto.createHash('sha384').update(data, 'utf8').digest('hex');
const a = Buffer.from(String(headerSig || ''), 'utf8');
const b = Buffer.from(expected, 'utf8');
return a.length === b.length && crypto.timingSafeEqual(a, b); // timing-safe
}
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 306 B
- examples/express/package.json 395 B
- examples/express/README.md 1.6 KB
- examples/express/src/index.js 6.3 KB runs code
- examples/express/test/webhook.test.js 4.8 KB runs code
- examples/fastapi/.env.example 236 B
- examples/fastapi/main.py 5.6 KB runs code
- examples/fastapi/README.md 1.6 KB
- examples/fastapi/requirements.txt 61 B
- examples/fastapi/test_webhook.py 4.2 KB runs code
- examples/nextjs/.env.example 236 B
- examples/nextjs/app/webhooks/praxis/route.ts 5.4 KB runs code
- examples/nextjs/package.json 490 B
- examples/nextjs/README.md 1.4 KB
- examples/nextjs/test/webhook.test.ts 5.1 KB runs code
- examples/nextjs/vitest.config.ts 140 B runs code
- references/overview.md 4.4 KB
- references/setup.md 2.4 KB
- references/verification.md 6.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.
- 2d ago First seen · 177 lines · 73 tokens per session scan A e25e2196614e
praxis-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 2,077 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…