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/azure-event-grid-webhooksnpx skills add hookdeck/webhook-skills --skill azure-event-grid-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/azure-event-grid-webhooks)<a href="https://agentmods.dev/skills/hookdeck/webhook-skills/azure-event-grid-webhooks"><img src="https://agentmods.dev/badge/skills/hookdeck/webhook-skills/azure-event-grid-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.00148 | $0.04105 |
| Opus 5 | $0.00074 | $0.02053 |
| Sonnet 5 | $0.00030 | $0.00821 |
| Haiku 4.5 | $0.00015 | $0.00411 |
Grade A, and why
azure-event-grid-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 6d 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 — 326 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Azure Event Grid Webhooks
When to Use This Skill
- How do I receive Azure Event Grid events at an HTTP endpoint?
- How do I verify an Azure Event Grid webhook? Where is the signature header?
- How do I handle
Microsoft.EventGrid.SubscriptionValidationEvent? - Why is my Event Grid event subscription stuck in
AwaitingManualActionorFailed? - What is
WebHook-Request-Origin/WebHook-Allowed-Originand why is Event Grid sending me an HTTP OPTIONS request? - How do I authenticate Event Grid deliveries with a custom header, a query-parameter secret, or Microsoft Entra ID?
- How do I parse
Microsoft.Storage.BlobCreatedfrom an Event Grid array vs a CloudEvents object?
There Is No Signature — Read This First
Event Grid is a managed pub/sub broker, not a single-vendor webhook signer.
- Event Grid does not sign the request body. There is no
X-Signature, no HMAC, no shared signing secret, no timestamp+signature pair, no asymmetric signature. Do not write acrypto.createHmac/hmac.newverifier for Event Grid — there is nothing to verify against. - Security comes from two other things, and a production handler needs both:
| Layer | What it proves | Mechanism |
|---|---|---|
| Handshake (subscription time) | You own the endpoint and expected this subscription | SubscriptionValidationEvent echo, or the CloudEvents OPTIONS preflight |
| Channel auth (every delivery) | The caller is who you configured | A static delivery-property header you choose, a client secret in a query parameter, or a Microsoft Entra ID bearer token |
- Because nothing is signed, there is no raw-body requirement. Parsing JSON before authenticating is safe here in a way it never is for Stripe or Shopify.
If you are looking at Hookdeck's
AZURE_EVENT_GRIDsource config and see HMAC / Basic Auth / API Key options: those configure a header you attach via Event Grid delivery properties. Azure computes no HMAC over the payload.
What ships with it
22 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 2.5 KB
- examples/express/package.json 444 B
- examples/express/README.md 4.9 KB
- examples/express/src/eventgrid.js 12 KB runs code
- examples/express/src/index.js 5.8 KB runs code
- examples/express/test/webhook.test.js 20 KB runs code
- examples/fastapi/.env.example 2.5 KB
- examples/fastapi/main.py 18 KB runs code
- examples/fastapi/README.md 2.9 KB
- examples/fastapi/requirements.txt 424 B
- examples/fastapi/test_webhook.py 15 KB runs code
- examples/nextjs/.env.example 2.5 KB
- examples/nextjs/app/webhooks/azure-event-grid/route.ts 5.0 KB runs code
- examples/nextjs/lib/eventgrid.ts 13 KB runs code
- examples/nextjs/package.json 605 B
- examples/nextjs/README.md 4.7 KB
- examples/nextjs/test/webhook.test.ts 20 KB runs code
- examples/nextjs/tsconfig.json 411 B
- examples/nextjs/vitest.config.ts 140 B runs code
- references/overview.md 12 KB
- references/setup.md 12 KB
- references/verification.md 17 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.
- 6d ago First seen · 326 lines · 148 tokens per session scan A 7420ec18cf27
azure-event-grid-webhooks is a skill published in the GitHub repository hookdeck/webhook-skills (84 stars, last pushed 2d ago), licensed MIT. It adds 148 tokens to every session and 4,105 once invoked, about $0.0007 per session on Opus 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-08-30.
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…
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…
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…