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/pylon-webhooksnpx skills add hookdeck/webhook-skills --skill pylon-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/pylon-webhooks)<a href="https://agentmods.dev/skills/hookdeck/webhook-skills/pylon-webhooks"><img src="https://agentmods.dev/badge/skills/hookdeck/webhook-skills/pylon-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.00081 | $0.01770 |
| Opus 5 | $0.00041 | $0.00885 |
| Sonnet 5 | $0.00016 | $0.00354 |
| Haiku 4.5 | $0.00008 | $0.00177 |
Grade A, and why
pylon-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
73% identical to adyen-webhooks — 184 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 — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pylon Webhooks
Pylon is a B2B customer support platform. It delivers webhooks to a webhook destination you configure, signed with HMAC-SHA256. There is no official Pylon SDK — verify manually in every framework.
When to Use This Skill
- How do I receive Pylon webhooks?
- How do I verify Pylon webhook signatures?
- Why is my Pylon
Pylon-Webhook-Signatureverification failing? - How do I handle Pylon issue events like
issue.createdorissue.updated?
Verification (core)
Pylon sends three headers with every delivery:
| Header | Example | Purpose |
|---|---|---|
Pylon-Webhook-Signature |
hs256=9f8c… |
HMAC-SHA256 signature, hs256= prefix + hex digest |
Pylon-Webhook-Timestamp |
1624235417 |
Unix seconds, part of the signed content |
Pylon-Webhook-Version |
2021-07 |
Payload schema version |
The signed content is timestamp + "." + rawBody. Compute HMAC-SHA256 with your
destination's secret (shown only once when you create the destination),
prefix with hs256=, and compare against the header using a timing-safe check.
Always verify against the raw request body — do not JSON.parse first.
Node (node:crypto, no dependency):
const crypto = require('crypto');
function verifyPylonWebhook(rawBody, timestamp, signatureHeader, secret) {
if (!signatureHeader || !timestamp) return false;
const expected = 'hs256=' + crypto
.createHmac('sha256', secret)
.update(`${timestamp}.`) // Pylon signs timestamp + "." + rawBody
.update(rawBody) // rawBody is a Buffer/string, never parsed JSON
.digest('hex');
try {
return crypto.timingSafeEqual(Buffer.from(signatureHeader), Buffer.from(expected));
} catch {
return false; // length mismatch = invalid
}
}
Python (hmac, no dependency):
import hmac, hashlib
def verify_pylon_webhook(raw_body: bytes, timestamp: str, signature_header: str, secret: str) -> bool:
if not signature_header or not timestamp:
return False
signed = timestamp.encode() + b"." + raw_body # timestamp + "." + rawBody
expected = "hs256=" + hmac.new(secret.encode(), signed, hashlib.sha256).hexdigest()
return hmac.compare_digest(signature_header, expected)
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 134 B
- examples/express/package.json 366 B
- examples/express/README.md 1.6 KB
- examples/express/src/index.js 3.7 KB runs code
- examples/express/test/webhook.test.js 5.4 KB runs code
- examples/fastapi/.env.example 134 B
- examples/fastapi/main.py 3.0 KB runs code
- examples/fastapi/README.md 1.8 KB
- examples/fastapi/requirements.txt 82 B
- examples/fastapi/test_webhook.py 5.3 KB runs code
- examples/nextjs/.env.example 134 B
- examples/nextjs/app/webhooks/pylon/route.ts 3.0 KB runs code
- examples/nextjs/package.json 478 B
- examples/nextjs/README.md 1.6 KB
- examples/nextjs/test/webhook.test.ts 3.1 KB runs code
- examples/nextjs/vitest.config.ts 140 B runs code
- references/overview.md 3.2 KB
- references/setup.md 2.7 KB
- references/verification.md 4.1 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 · 155 lines · 81 tokens per session scan A 5a35fbb734ff
pylon-webhooks is a skill published in the GitHub repository hookdeck/webhook-skills (84 stars, last pushed yesterday), licensed MIT. It adds 81 tokens to every session and 1,770 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 73% identical to adyen-webhooks, differing in 184 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…
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…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…