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/gitlab-webhooksnpx skills add hookdeck/webhook-skills --skill gitlab-webhooksgit clone --depth 1 https://github.com/hookdeck/webhook-skillsWhat 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.00043 | $0.01842 |
| Opus 5 | $0.00022 | $0.00921 |
| Sonnet 5 | $0.00009 | $0.00368 |
| Haiku 4.5 | $0.00004 | $0.00184 |
Grade A, and why
gitlab-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
84% identical to adyen-webhooks — 213 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 — 186 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitLab Webhooks
When to Use This Skill
- Setting up GitLab webhook handlers
- Debugging webhook token verification failures
- Understanding GitLab event types and payloads
- Handling push, merge request, issue, or pipeline events
Essential Code (USE THIS)
GitLab Token Verification (JavaScript)
function verifyGitLabWebhook(tokenHeader, secret) {
if (!tokenHeader || !secret) return false;
// GitLab uses simple token comparison (not HMAC)
// Use timing-safe comparison to prevent timing attacks
try {
return crypto.timingSafeEqual(
Buffer.from(tokenHeader),
Buffer.from(secret)
);
} catch {
return false;
}
}
Express Webhook Handler
const express = require('express');
const crypto = require('crypto');
const app = express();
// CRITICAL: Use express.json() - GitLab sends JSON payloads
app.post('/webhooks/gitlab',
express.json(),
(req, res) => {
const token = req.headers['x-gitlab-token'];
const event = req.headers['x-gitlab-event'];
const eventUUID = req.headers['x-gitlab-event-uuid'];
// Verify token
if (!verifyGitLabWebhook(token, process.env.GITLAB_WEBHOOK_TOKEN)) {
console.error('GitLab token verification failed');
return res.status(401).send('Unauthorized');
}
console.log(`Received ${event} (UUID: ${eventUUID})`);
// Handle by event type
const objectKind = req.body.object_kind;
switch (objectKind) {
case 'push':
console.log(`Push to ${req.body.ref}:`, req.body.commits?.length, 'commits');
break;
case 'merge_request':
console.log(`MR !${req.body.object_attributes?.iid} ${req.body.object_attributes?.action}`);
break;
case 'issue':
console.log(`Issue #${req.body.object_attributes?.iid} ${req.body.object_attributes?.action}`);
break;
case 'pipeline':
console.log(`Pipeline ${req.body.object_attributes?.id} ${req.body.object_attributes?.status}`);
break;
default:
console.log('Received event:', objectKind || event);
}
res.json({ received: true });
}
);
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 173 B
- examples/express/package.json 412 B
- examples/express/README.md 1.4 KB
- examples/express/src/index.js 6.2 KB runs code
- examples/express/test/webhook.test.js 10 KB runs code
- examples/fastapi/.env.example 173 B
- examples/fastapi/main.py 7.3 KB runs code
- examples/fastapi/README.md 1.7 KB
- examples/fastapi/requirements.txt 104 B
- examples/fastapi/test_webhook.py 12 KB runs code
- examples/nextjs/.env.example 119 B
- examples/nextjs/app/webhooks/gitlab/route.ts 7.5 KB runs code
- examples/nextjs/package.json 555 B
- examples/nextjs/README.md 1.7 KB
- examples/nextjs/test/webhook.test.ts 14 KB runs code
- examples/nextjs/vitest.config.ts 192 B runs code
- references/overview.md 3.0 KB
- references/setup.md 3.4 KB
- references/verification.md 4.5 KB
- TODO.md 1.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 · 186 lines · 43 tokens per session scan A 3a0ac4e8c31e
gitlab-webhooks is a skill published in the GitHub repository hookdeck/webhook-skills (83 stars, last pushed 5d ago), licensed MIT. It adds 43 tokens to every session and 1,842 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 84% identical to adyen-webhooks, differing in 213 lines, and is treated as a copy.
Other skills, from other repositories
using-git-worktrees
Use when a coding task needs a concurrent checkout, unrelated dirty state blocks safe branch switching, or the user or repository explicitly requires a worktree.
memstack-content-product-description
Use this skill when the user says 'product description', 'product listing', 'product copy', 'Amazon listing', 'Shopify listing', 'e-commerce copy', or needs conversion-optimized product descriptions with benefit-driven headlines and platform-specific SEO. Do NOT use for pricing strategy or sales funnels.
ai-slop
Operational rubric that turns "don't make AI slop" into observable properties, severity levels, evidence requirements, and repair actions for interface design. Use as the reference rubric when building or reviewing marketing sites, product interfaces, dashboards, portfolios, or e-commerce pages, especially alongside…
om-gap-analysis
Grounded platform gap analysis at engagement scale — turn a folder of client docs into an Epic/Story tree where every coverage verdict is re-run by executable gates against a validated checkout of the platform, scored in atomic commits, license-tier-tagged, and synthesized into a client-facing summary + backlog. Use…
using-git-worktrees
Creates and manages isolated Git worktrees for parallel agents, risky experiments, or long-running feature work while preserving the user's current checkout. Use before concurrent branch edits or when isolation makes rollback safer. Not for a trivial one-file change that is already isolated.
agent-prompts-warmup
Audit and sync agent instruction files across all coding agent formats. FRE (first-run) checks scaffolding completeness; ongoing use keeps files in sync after edits.