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 skills add hookdeck/webhook-skills --skill polytomic-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/polytomic-webhooks)<a href="https://agentmods.dev/skills/hookdeck/webhook-skills/polytomic-webhooks"><img src="https://agentmods.dev/badge/skills/hookdeck/webhook-skills/polytomic-webhooks/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/hookdeck/webhook-skills/polytomic-webhooks"><img src="https://agentmods.dev/badge/skills/hookdeck/webhook-skills/polytomic-webhooks.svg" alt="Reviewed on agentmods" width="80" 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.00171 | $0.04620 |
| Opus 5.5 | $0.00068 | $0.01848 |
| Sonnet 5.5 | $0.00034 | $0.00924 |
| Haiku 4.5 | $0.00017 | $0.00462 |
Grade A, and why
polytomic-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 14d 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 — 333 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Polytomic Webhooks
Polytomic (polytomic.com) is a data-movement platform — models, Model Syncs and Bulk Syncs that move data between warehouses, SaaS apps and databases (reverse ETL). Its one outbound-HTTP surface is the Webhook connection used as a sync destination: you add a Webhook connection, point a Model Sync at it, and Polytomic POSTs batches of changed records to your URL on the sync's schedule.
Frame this as "receive Polytomic sync record batches", not "subscribe to Polytomic events." There is no event-subscription UI, no per-event-type toggles and no separate platform-events API. Polytomic is not an event producer in the usual sense.
Three things make Polytomic unlike most providers in this repo:
- There is no signature. No HMAC, no digest, no signing secret. The only
authentication is a static shared bearer token in the
Authorizationheader, matching the Secret shown during connection setup. Verbatim from the docs: "This should be a 'Bearer' token matching the same value that was provided as the 'Secret' during connection setup. For now, this is the only request authorization and is a static value." Polytomic-Signature-Timestampis NOT a signature, despite the name. It carries only an RFC 3339 / ISO 8601 UTC timestamp (2021-06-01T22:55:36Z) — not a Unix epoch integer and not a digest. Parse it withnew Date(value)/datetime.fromisoformat, neverparseInt.- Every payload is a batch.
object.recordsis "a list of the records changed since the last payload" — default batch size 100, and user-configurable. Every handler must loop. Never assume one record.
When to Use This Skill
- How do I receive Polytomic webhooks?
- How do I verify a Polytomic webhook signature? (You can't — there is none. Compare the bearer token instead.)
- What do I do with the
Polytomic-Signature-Timestampheader? (Freshness only — it is not a signature.) - Should I HMAC the timestamp plus the body? (No. There is nothing to compare an HMAC against.)
- Is the
Authorizationbearer token a JWT I should verify? (No — treat it as an opaque secret and compare byte-for-byte.) - Which Polytomic webhook event types exist? (Exactly one:
sync.records.) - How do I loop over
object.records[]and usehashfor deduplication? - Why are the keys inside
fieldsdifferent from the docs' example? (They are defined by your sync configuration.) - Why did my Polytomic sync show as failed? (Your endpoint returned 4xx/5xx.)
- Why was my first webhook batch enormous? (The first sync run backfills everything.)
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 1.1 KB
- examples/express/package.json 431 B
- examples/express/README.md 6.1 KB
- examples/express/src/index.js 14 KB runs code
- examples/express/test/webhook.test.js 14 KB runs code
- examples/fastapi/.env.example 1.1 KB
- examples/fastapi/main.py 14 KB runs code
- examples/fastapi/README.md 7.7 KB
- examples/fastapi/requirements.txt 82 B
- examples/fastapi/test_webhook.py 16 KB runs code
- examples/nextjs/.env.example 1.1 KB
- examples/nextjs/app/webhooks/polytomic/route.ts 13 KB runs code
- examples/nextjs/package.json 552 B
- examples/nextjs/README.md 6.7 KB
- examples/nextjs/test/webhook.test.ts 14 KB runs code
- examples/nextjs/vitest.config.ts 140 B runs code
- references/overview.md 6.8 KB
- references/setup.md 8.2 KB
- references/verification.md 13 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.
- 14d ago First seen · 333 lines · 171 tokens per session scan A 658ee5f7beff
polytomic-webhooks is a skill published in the GitHub repository hookdeck/webhook-skills (92 stars, last pushed yesterday), licensed MIT. It adds 171 tokens to every session and 4,620 once invoked, about $0.0007 per session on Opus 5.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-10-03.
Other skills, from other repositories
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…