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/xero-webhooksnpx skills add hookdeck/webhook-skills --skill xero-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/xero-webhooks)<a href="https://agentmods.dev/skills/hookdeck/webhook-skills/xero-webhooks"><img src="https://agentmods.dev/badge/skills/hookdeck/webhook-skills/xero-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.00066 | $0.01950 |
| Opus 5 | $0.00033 | $0.00975 |
| Sonnet 5 | $0.00013 | $0.00390 |
| Haiku 4.5 | $0.00007 | $0.00195 |
Grade A, and why
xero-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
89% identical to adyen-webhooks — 187 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 — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Xero Webhooks
When to Use This Skill
- How do I receive Xero webhooks?
- How do I verify the
x-xero-signatureheader? - Why is my Xero webhook stuck as "inactive" / failing Intent to Receive (ITR)?
- How do I handle
CONTACT,INVOICE,CREDITNOTE, orSUBSCRIPTIONevents? - How do I fetch the changed record from a Xero webhook payload?
Verification (core)
Xero signs the raw request body with HMAC-SHA256 keyed on the app's webhook signing key, base64-encodes the digest, and sends it in the x-xero-signature header. Capture the raw body before JSON parsing (parsing re-serializes the bytes and breaks the HMAC). Compare timing-safe. The official SDKs (xero-node, xero-python) do not ship a webhook-signature helper — verify manually.
Node:
const crypto = require('crypto');
function verifyXeroSignature(rawBody, signatureHeader, signingKey) {
if (!signatureHeader) return false;
const expected = crypto.createHmac('sha256', signingKey).update(rawBody).digest('base64');
try {
return crypto.timingSafeEqual(Buffer.from(signatureHeader), Buffer.from(expected));
} catch {
return false; // length mismatch = invalid
}
}
Python:
import hmac, hashlib, base64
def verify_xero_signature(raw_body: bytes, signature_header: str, signing_key: str) -> bool:
if not signature_header:
return False
expected = base64.b64encode(
hmac.new(signing_key.encode(), raw_body, hashlib.sha256).digest()
).decode()
return hmac.compare_digest(signature_header, expected)
Intent to Receive (ITR): When you save the endpoint, Xero POSTs validation payloads and your server MUST respond within a few seconds: HTTP 200 when the signature matches, HTTP 401 when it does not. Anything else (including a 400) fails ITR and leaves the webhook inactive. Return
401— not400— for a bad signature. The same verify-then-200/401 logic serves both ITR probes and real events.
For complete handlers with route wiring, event dispatch, and tests, see:
What ships with it
20 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 188 B
- examples/express/package.json 392 B
- examples/express/README.md 1.6 KB
- examples/express/src/index.js 4.6 KB runs code
- examples/express/test/webhook.test.js 6.0 KB runs code
- examples/fastapi/.env.example 139 B
- examples/fastapi/main.py 3.8 KB runs code
- examples/fastapi/README.md 1.6 KB
- examples/fastapi/requirements.txt 102 B
- examples/fastapi/test_webhook.py 5.9 KB runs code
- examples/nextjs/.env.example 139 B
- examples/nextjs/app/webhooks/xero/route.ts 3.9 KB runs code
- examples/nextjs/package.json 504 B
- examples/nextjs/README.md 1.5 KB
- examples/nextjs/test/webhook.test.ts 3.7 KB runs code
- examples/nextjs/tsconfig.json 562 B
- examples/nextjs/vitest.config.ts 140 B runs code
- references/overview.md 4.8 KB
- references/setup.md 3.6 KB
- references/verification.md 4.6 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 · 156 lines · 66 tokens per session scan A 9767f43d894a
xero-webhooks is a skill published in the GitHub repository hookdeck/webhook-skills (84 stars, last pushed 2d ago), licensed MIT. It adds 66 tokens to every session and 1,950 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 89% identical to adyen-webhooks, differing in 187 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…
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…