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 docker-hub-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/docker-hub-webhooks)<a href="https://agentmods.dev/skills/hookdeck/webhook-skills/docker-hub-webhooks"><img src="https://agentmods.dev/badge/skills/hookdeck/webhook-skills/docker-hub-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/docker-hub-webhooks"><img src="https://agentmods.dev/badge/skills/hookdeck/webhook-skills/docker-hub-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.00135 | $0.04046 |
| Opus 5.5 | $0.00054 | $0.01618 |
| Sonnet 5.5 | $0.00027 | $0.00809 |
| Haiku 4.5 | $0.00014 | $0.00405 |
Grade A, and why
docker-hub-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 18d 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 — 295 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Docker Hub Webhooks
Docker Hub (hub.docker.com) is Docker Inc.'s container image registry. A Docker Hub repository webhook is configured per repository (repository → Webhooks tab → name + destination URL → Create) and fires on a push to that repository.
Two things make Docker Hub unlike most providers in this repo, and both must be reflected in your handler:
- There is no signature verification. None. No signature header, no shared secret, no HMAC, no timestamp, no token field, no auth option. The create form takes exactly two inputs — a name and a destination URL. You cannot verify that a POST came from Docker Hub.
- There is no event type. Docker Hub webhooks have exactly one trigger —
a push — and the payload carries no
event,typeoractionfield, and the request carries noX-...-Eventheader. Do not writeswitch (event.type). Route onrepository.repo_nameandpush_data.tag.
Scope note: this skill covers Docker Hub repository webhooks only. It does
not cover Docker Build Cloud, Docker Scout integrations, the self-hosted
distribution registry's notifications: endpoints (a different envelope, with
its own optional custom headers), GitHub Container Registry registry_package
webhooks, or Docker Engine events. Do not borrow payloads or auth from those.
When to Use This Skill
- How do I receive Docker Hub webhooks?
- How do I verify a Docker Hub webhook signature? (You can't — there is none.)
- Is there an
X-Docker-Signature/X-Hub-Signatureheader on Docker Hub webhooks? (No.) - How do I secure an unsigned Docker Hub push webhook endpoint?
- How do I read
push_data.tag,push_data.pusherandrepository.repo_name? - Which Docker Hub webhook event types exist? (One trigger, no event field.)
- What do I do with
callback_url? (Nothing — it is legacy and unsupported.) - How do I handle
dhi_metadataon a mirrored Docker Hardened Image repository? - Where is the image digest in the payload? (Not there — look it up via the Hub API.)
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 1.8 KB
- examples/express/package.json 424 B
- examples/express/README.md 4.7 KB
- examples/express/src/index.js 14 KB runs code
- examples/express/test/webhook.test.js 13 KB runs code
- examples/fastapi/.env.example 1.8 KB
- examples/fastapi/main.py 14 KB runs code
- examples/fastapi/README.md 4.8 KB
- examples/fastapi/requirements.txt 82 B
- examples/fastapi/test_webhook.py 13 KB runs code
- examples/nextjs/.env.example 1.7 KB
- examples/nextjs/app/webhooks/docker-hub/[token]/route.ts 13 KB runs code
- examples/nextjs/app/webhooks/docker-hub/route.ts 1.5 KB runs code
- examples/nextjs/package.json 534 B
- examples/nextjs/README.md 4.8 KB
- examples/nextjs/test/webhook.test.ts 14 KB runs code
- examples/nextjs/vitest.config.ts 140 B runs code
- references/overview.md 11 KB
- references/setup.md 7.7 KB
- references/verification.md 12 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.
- 18d ago First seen · 295 lines · 135 tokens per session scan A f469e14813e7
docker-hub-webhooks is a skill published in the GitHub repository hookdeck/webhook-skills (92 stars, last pushed yesterday), licensed MIT. It adds 135 tokens to every session and 4,046 once invoked, about $0.0005 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-09-29.
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…