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/monday-webhooksnpx skills add hookdeck/webhook-skills --skill monday-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/monday-webhooks)<a href="https://agentmods.dev/skills/hookdeck/webhook-skills/monday-webhooks"><img src="https://agentmods.dev/badge/skills/hookdeck/webhook-skills/monday-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.00056 | $0.01751 |
| Opus 5 | $0.00028 | $0.00875 |
| Sonnet 5 | $0.00011 | $0.00350 |
| Haiku 4.5 | $0.00006 | $0.00175 |
Grade A, and why
monday-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 2d 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 — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
monday.com Webhooks
When to Use This Skill
- Setting up monday.com webhook handlers
- Implementing the
challengehandshake required at registration - Debugging JWT (
Authorizationheader) verification failures - Understanding monday.com event types and the
eventpayload wrapper - Handling board, column, subitem, and update events
Two things every monday.com endpoint must do
monday.com webhooks are unusual — there are two separate checks, not one:
- Challenge handshake (required). When a webhook is created, monday.com POSTs
{ "challenge": "<token>" }. Your endpoint must echo it back as{ "challenge": "<token>" }or registration fails. This is the only check guaranteed for every webhook, including no-code and personal-token webhooks. - JWT verification (when present). For webhooks created by an integration
app, monday.com signs each request with a JWT in the
Authorizationheader (HS256), signed with your app's Signing Secret. Verify it with a JWT library. Webhooks created with a personal API token or the no-code board integration may not send this header.
monday.com does not follow the Standard Webhooks spec, and the JWT is not an HMAC over the request body — it is a self-contained token that authenticates the sender. Because verification never reads the body, parsing JSON before verifying is safe here (unlike Stripe/GitHub HMAC schemes).
Verification (core)
import { jwtVerify } from 'jose';
// monday.com signs each request with a JWT in the Authorization header (HS256),
// signed with your app's Signing Secret (board webhooks) or Client Secret
// (app lifecycle webhooks). jwtVerify throws on a bad signature or expiry.
async function verifyMondayJwt(authHeader, secret) {
if (!authHeader) throw new Error('Missing Authorization header');
const token = authHeader.startsWith('Bearer ')
? authHeader.slice(7)
: authHeader; // monday sends the raw token
const { payload } = await jwtVerify(
token,
new TextEncoder().encode(secret),
{ algorithms: ['HS256'] }
);
return payload; // { accountId, userId, aud, exp, iat, ... }
}
// On registration monday POSTs { "challenge": "<token>" } — echo it back first:
// if (body.challenge) return res.status(200).json({ challenge: body.challenge });
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 431 B
- examples/express/package.json 470 B
- examples/express/README.md 1.6 KB
- examples/express/src/index.js 4.4 KB runs code
- examples/express/test/webhook.test.js 5.0 KB runs code
- examples/fastapi/.env.example 431 B
- examples/fastapi/main.py 4.5 KB runs code
- examples/fastapi/README.md 1.7 KB
- examples/fastapi/requirements.txt 96 B
- examples/fastapi/test_webhook.py 3.7 KB runs code
- examples/nextjs/.env.example 431 B
- examples/nextjs/app/webhooks/monday/route.ts 4.1 KB runs code
- examples/nextjs/package.json 506 B
- examples/nextjs/README.md 1.5 KB
- examples/nextjs/test/webhook.test.ts 4.2 KB runs code
- examples/nextjs/vitest.config.ts 140 B runs code
- references/overview.md 4.0 KB
- references/setup.md 3.5 KB
- references/verification.md 5.3 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.
- 2d ago First seen · 160 lines · 56 tokens per session scan A 167786f61543
monday-webhooks is a skill published in the GitHub repository hookdeck/webhook-skills (84 stars, last pushed yesterday), licensed MIT. It adds 56 tokens to every session and 1,751 once invoked, about $0.0003 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-09-03.
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…
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…