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/pipedrive-webhooksnpx skills add hookdeck/webhook-skills --skill pipedrive-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/pipedrive-webhooks)<a href="https://agentmods.dev/skills/hookdeck/webhook-skills/pipedrive-webhooks"><img src="https://agentmods.dev/badge/skills/hookdeck/webhook-skills/pipedrive-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.00047 | $0.01766 |
| Opus 5 | $0.00023 | $0.00883 |
| Sonnet 5 | $0.00009 | $0.00353 |
| Haiku 4.5 | $0.00005 | $0.00177 |
Grade A, and why
pipedrive-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.
This is a copy
78% identical to adyen-webhooks — 186 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pipedrive Webhooks
When to Use This Skill
- How do I receive Pipedrive webhooks?
- How do I authenticate Pipedrive webhook deliveries?
- How do I handle
create.deal,change.person, ordelete.activityevents? - Why is my Pipedrive webhook returning 401 / getting banned?
- How do I create a Pipedrive webhook (v2) via the API?
Verification (core)
Pipedrive does NOT sign webhooks. There is no HMAC, no signature header, and
it is not Standard Webhooks compliant. Security is HTTP Basic Auth: you
set http_auth_user / http_auth_password when creating the webhook, and
Pipedrive sends them in the standard Authorization: Basic <base64(user:pass)>
header on every delivery. Your endpoint must be HTTPS (self-signed certs are not
supported). Verify the credentials with a timing-safe comparison:
const crypto = require('crypto');
function safeEqual(a, b) {
const ab = Buffer.from(a, 'utf8');
const bb = Buffer.from(b, 'utf8');
// Length check first: timingSafeEqual throws on unequal-length buffers
return ab.length === bb.length && crypto.timingSafeEqual(ab, bb);
}
function verifyBasicAuth(authHeader, user, pass) {
if (!authHeader || !authHeader.startsWith('Basic ')) return false;
const decoded = Buffer.from(authHeader.slice(6), 'base64').toString('utf8');
const sep = decoded.indexOf(':'); // password may contain ':'
if (sep === -1) return false;
return safeEqual(decoded.slice(0, sep), user) && safeEqual(decoded.slice(sep + 1), pass);
}
For complete handlers with route wiring, event dispatch, and tests, see:
Event Format
Pipedrive v2 event types are action.entity (e.g. create.deal). The payload
does not contain a combined string — build it from meta.action and
meta.entity:
const event = `${body.meta.action}.${body.meta.entity}`; // e.g. "change.person"
What ships with it
21 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 461 B
- examples/express/package.json 446 B
- examples/express/README.md 1.6 KB
- examples/express/register-webhook.js 1.2 KB runs code
- examples/express/src/index.js 3.4 KB runs code
- examples/express/test/webhook.test.js 3.3 KB runs code
- examples/fastapi/.env.example 250 B
- examples/fastapi/main.py 3.2 KB runs code
- examples/fastapi/README.md 1.5 KB
- examples/fastapi/requirements.txt 82 B
- examples/fastapi/test_webhook.py 4.1 KB runs code
- examples/nextjs/.env.example 439 B
- examples/nextjs/app/webhooks/pipedrive/route.ts 3.2 KB runs code
- examples/nextjs/package.json 583 B
- examples/nextjs/README.md 1.6 KB
- examples/nextjs/register-webhook.js 1.2 KB runs code
- examples/nextjs/test/webhook.test.ts 3.2 KB runs code
- examples/nextjs/vitest.config.ts 140 B runs code
- references/overview.md 3.9 KB
- references/setup.md 3.3 KB
- references/verification.md 4.6 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 · 149 lines · 47 tokens per session scan A 445c36fd6656
pipedrive-webhooks is a skill published in the GitHub repository hookdeck/webhook-skills (84 stars, last pushed yesterday), licensed MIT. It adds 47 tokens to every session and 1,766 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 78% identical to adyen-webhooks, differing in 186 lines, and is treated as a copy.
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…