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/bitbucket-webhooksnpx skills add hookdeck/webhook-skills --skill bitbucket-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/bitbucket-webhooks)<a href="https://agentmods.dev/skills/hookdeck/webhook-skills/bitbucket-webhooks"><img src="https://agentmods.dev/badge/skills/hookdeck/webhook-skills/bitbucket-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.00066 | $0.01464 |
| Opus 5 | $0.00033 | $0.00732 |
| Sonnet 5 | $0.00013 | $0.00293 |
| Haiku 4.5 | $0.00007 | $0.00146 |
Grade A, and why
bitbucket-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 3d 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
83% identical to adyen-webhooks — 168 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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bitbucket Webhooks
When to Use This Skill
- Setting up Bitbucket Cloud webhook handlers
- Debugging Bitbucket signature verification failures
- Understanding Bitbucket event keys and payloads
- Handling repo:push, pull request, or issue events
Verification (core)
Bitbucket signs the raw request body with HMAC-SHA256 keyed on your webhook
secret and sends the digest in the X-Hub-Signature header formatted as
sha256=<hex> (the prefix names the algorithm — currently sha256). Pass the
raw body, and compare timing-safe. Webhooks configured without a secret are
unsigned and send no X-Hub-Signature header.
Node:
const crypto = require('crypto');
function verify(rawBody, signatureHeader, secret) {
const [algo, sig] = (signatureHeader || '').split('=');
if (algo !== 'sha256' || !sig) return false;
const expected = crypto.createHmac('sha256', secret).update(rawBody).digest('hex');
try {
return crypto.timingSafeEqual(Buffer.from(sig), Buffer.from(expected));
} catch {
return false;
}
}
Python:
import hmac, hashlib
def verify(raw_body: bytes, signature_header: str, secret: str) -> bool:
algo, _, sig = (signature_header or "").partition("=")
if algo != "sha256" or not sig:
return False
expected = hmac.new(secret.encode(), raw_body, hashlib.sha256).hexdigest()
return hmac.compare_digest(sig, expected)
For complete handlers with route wiring, event dispatch, and tests, see:
Common Event Types
| Event Key | Description |
|---|---|
repo:push |
Commits pushed to a branch or tag |
pullrequest:created |
Pull request opened |
pullrequest:updated |
Pull request title/description/commits updated |
pullrequest:approved |
Pull request approved by a reviewer |
pullrequest:fulfilled |
Pull request merged |
pullrequest:rejected |
Pull request declined |
pullrequest:comment_created |
Comment added to a pull request |
issue:created |
Issue created |
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 116 B
- examples/express/package.json 429 B
- examples/express/README.md 1.0 KB
- examples/express/src/index.js 4.2 KB runs code
- examples/express/test/webhook.test.js 6.0 KB runs code
- examples/fastapi/.env.example 116 B
- examples/fastapi/main.py 3.8 KB runs code
- examples/fastapi/README.md 1.0 KB
- examples/fastapi/requirements.txt 92 B
- examples/fastapi/test_webhook.py 6.0 KB runs code
- examples/nextjs/.env.example 116 B
- examples/nextjs/app/webhooks/bitbucket/route.ts 3.5 KB runs code
- examples/nextjs/package.json 563 B
- examples/nextjs/README.md 881 B
- examples/nextjs/test/webhook.test.ts 5.1 KB runs code
- examples/nextjs/vitest.config.ts 140 B runs code
- references/overview.md 3.6 KB
- references/setup.md 3.1 KB
- references/verification.md 5.6 KB
- TODO.md 2.5 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.
- 3d ago First seen · 137 lines · 66 tokens per session scan A 0f8dc4b81be2
bitbucket-webhooks is a skill published in the GitHub repository hookdeck/webhook-skills (84 stars, last pushed 7d ago), licensed MIT. It adds 66 tokens to every session and 1,464 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 83% identical to adyen-webhooks, differing in 168 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…