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/nmi-webhooksnpx skills add hookdeck/webhook-skills --skill nmi-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/nmi-webhooks)<a href="https://agentmods.dev/skills/hookdeck/webhook-skills/nmi-webhooks"><img src="https://agentmods.dev/badge/skills/hookdeck/webhook-skills/nmi-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.00123 | $0.02029 |
| Opus 5 | $0.00062 | $0.01014 |
| Sonnet 5 | $0.00025 | $0.00406 |
| Haiku 4.5 | $0.00012 | $0.00203 |
Grade A, and why
nmi-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.
This is a copy
81% identical to adyen-webhooks — 198 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 — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
NMI Webhooks
When to Use This Skill
- How do I receive NMI (Network Merchants) webhooks?
- How do I verify the NMI
Webhook-Signatureheader? - Why is my NMI webhook signature verification failing?
- How do I handle
transaction.sale.success,transaction.auth.success,transaction.refund.success, ortransaction.void.successevents? - What is the
t=value in the NMI signature header — is it a timestamp?
How NMI Webhooks Work (Read This First)
NMI does not use the Standard Webhooks spec. Each delivery carries a single custom header:
Webhook-Signature: t=f3c1e9a2b7d84c15,s=9b7c...e10a
Two facts drive everything below:
tis a NONCE, not a timestamp. It is a random value NMI generates per delivery and includes in the signed content. Because it is not a timestamp, NMI documents no replay/timestamp tolerance window — do not try to reject "old" deliveries by parsingtas a Unix time.- The signature signs
"<nonce>.<raw_body>". You verify by computing HMAC-SHA256 over the nonce, a literal., and the raw, unparsed request body, keyed with your signing key, hex-encoding it, and comparing (timing -safe) to thesvalue. Re-serializing the JSON breaks the HMAC.
NMI ──POST body + "Webhook-Signature: t=<nonce>,s=<hex>"──▶ your endpoint
│ parse t + s
│ hmac_sha256(key, t + "." + rawBody)
▼
timing-safe compare hex == s → 200
The payload envelope is { "event_id", "event_type", "event_body" }. The
event_type is a dotted lowercase string like transaction.sale.success.
Verification (core)
const crypto = require('crypto');
// Header: "Webhook-Signature: t=<nonce>,s=<lowercase-hex-hmac>"
// t is a NONCE (not a timestamp); the signed content is `<nonce>.<rawBody>`.
function verifyNmiWebhook(rawBody, signatureHeader, signingKey) {
const parts = {};
for (const seg of String(signatureHeader || '').split(',')) {
const i = seg.indexOf('=');
if (i !== -1) parts[seg.slice(0, i).trim()] = seg.slice(i + 1).trim();
}
const { t: nonce, s: signature } = parts;
if (!nonce || !signature || !signingKey) return false;
const body = Buffer.isBuffer(rawBody) ? rawBody.toString('utf8') : rawBody;
const expected = crypto
.createHmac('sha256', signingKey)
.update(`${nonce}.${body}`)
.digest('hex');
try {
return crypto.timingSafeEqual(Buffer.from(expected), Buffer.from(signature));
} 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 233 B
- examples/express/package.json 360 B
- examples/express/README.md 1.6 KB
- examples/express/src/index.js 4.5 KB runs code
- examples/express/test/webhook.test.js 4.5 KB runs code
- examples/fastapi/.env.example 193 B
- examples/fastapi/main.py 3.6 KB runs code
- examples/fastapi/README.md 1.8 KB
- examples/fastapi/requirements.txt 82 B
- examples/fastapi/test_webhook.py 4.3 KB runs code
- examples/nextjs/.env.example 193 B
- examples/nextjs/app/webhooks/nmi/route.ts 3.6 KB runs code
- examples/nextjs/package.json 485 B
- examples/nextjs/README.md 1.6 KB
- examples/nextjs/test/webhook.test.ts 4.4 KB runs code
- examples/nextjs/vitest.config.ts 140 B runs code
- references/overview.md 4.7 KB
- references/setup.md 2.6 KB
- references/verification.md 5.2 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 · 169 lines · 123 tokens per session scan A 54c3961a2589
nmi-webhooks is a skill published in the GitHub repository hookdeck/webhook-skills (84 stars, last pushed yesterday), licensed MIT. It adds 123 tokens to every session and 2,029 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. It is 81% identical to adyen-webhooks, differing in 198 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…
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…