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 azure-logic-apps-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-logic-apps-webhooks)<a href="https://agentmods.dev/skills/hookdeck/webhook-skills/azure-logic-apps-webhooks"><img src="https://agentmods.dev/badge/skills/hookdeck/webhook-skills/azure-logic-apps-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/azure-logic-apps-webhooks"><img src="https://agentmods.dev/badge/skills/hookdeck/webhook-skills/azure-logic-apps-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.00098 | $0.02388 |
| Opus 5.5 | $0.00039 | $0.00955 |
| Sonnet 5.5 | $0.00020 | $0.00478 |
| Haiku 4.5 | $0.00010 | $0.00239 |
Grade A, and why
azure-logic-apps-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 — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Azure Logic Apps Webhooks
Covers outbound calls from the built-in HTTP action (and HTTP trigger) in Azure Logic Apps, Consumption or Standard, and the equivalent HTTP action in Power Automate. Your endpoint is the destination; the workflow decides the method, headers and body.
Not covered: the Logic Apps Request trigger (that's the workflow receiving
calls, secured with SAS sig parameters or Entra ID policies), and the HTTP
Webhook action's subscribe/callback protocol.
When to Use This Skill
- How do I receive a webhook from an Azure Logic App?
- How do I verify a Logic Apps HTTP action call? (There is no signature.)
- How do I check Basic authentication from Logic Apps in Express, Next.js or FastAPI?
- How do I use a shared secret header or Raw authentication with Logic Apps?
- Why does my Logic App get 401 from my webhook endpoint?
- Why does my Logic App keep polling my endpoint after I return 202?
Verification (core)
Logic Apps does not sign webhook payloads: no HMAC, no signature header, no timestamp. You authenticate the request with a credential configured on the HTTP action, and compare it in constant time:
| HTTP action setting | What arrives |
|---|---|
| Authentication = Basic (Username, Password) | Authorization: Basic base64(username:password) |
| Authentication = Raw (Value) | Authorization: <Value>, sent verbatim |
Headers (your own name, e.g. x-logic-apps-secret) |
That header with your secret |
const crypto = require('crypto');
// Hash first: equal-length buffers, no length leak, timingSafeEqual never throws.
const safeEqual = (a, b) => crypto.timingSafeEqual(
crypto.createHash('sha256').update(String(a)).digest(),
crypto.createHash('sha256').update(String(b)).digest());
function verifyBasicAuth(authorization, username, password) {
const m = /^Basic\s+([A-Za-z0-9+/=]+)\s*$/i.exec(authorization || '');
if (!m) return false;
const decoded = Buffer.from(m[1], 'base64').toString('utf8');
const sep = decoded.indexOf(':'); // first colon: passwords may contain ':'
if (sep === -1) return false;
const userOk = safeEqual(decoded.slice(0, sep), username);
const passOk = safeEqual(decoded.slice(sep + 1), password);
return userOk && passOk; // evaluate both, then combine
}
// Shared secret in a header (for Raw auth, the header is Authorization)
const verifySharedSecret = (value, secret) => Boolean(value && secret) && safeEqual(value, secret);
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 848 B
- examples/express/package.json 498 B
- examples/express/README.md 2.7 KB
- examples/express/src/index.js 5.4 KB runs code
- examples/express/test/webhook.test.js 7.4 KB runs code
- examples/fastapi/.env.example 848 B
- examples/fastapi/main.py 5.6 KB runs code
- examples/fastapi/README.md 2.9 KB
- examples/fastapi/requirements.txt 82 B
- examples/fastapi/test_webhook.py 6.3 KB runs code
- examples/nextjs/.env.example 824 B
- examples/nextjs/app/webhooks/azure-logic-apps/route.ts 4.9 KB runs code
- examples/nextjs/package.json 576 B
- examples/nextjs/README.md 2.7 KB
- examples/nextjs/test/webhook.test.ts 5.7 KB runs code
- examples/nextjs/vitest.config.ts 162 B runs code
- references/overview.md 3.3 KB
- references/setup.md 3.7 KB
- references/verification.md 5.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.
- 6d ago First seen · 174 lines · 98 tokens per session scan A ec4da3212950
azure-logic-apps-webhooks is a skill published in the GitHub repository hookdeck/webhook-skills (94 stars, last pushed today), licensed MIT. It adds 98 tokens to every session and 2,388 once invoked, about $0.0004 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-22.
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…