gitlab-webhooks

A guide for connecting an application to GitLab, a service for hosting code repositories, through webhook notifications. It explains how to receive events and check GitLab’s verification token.

In plain words
What is it for?
Use it for push, merge request, issue, pipeline, and release handlers.
Why use it?
It removes the guesswork from accepting GitLab notifications safely and handling their event data correctly.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/hookdeck/webhook-skills/gitlab-webhooks
Any agent
npx skills add hookdeck/webhook-skills --skill gitlab-webhooks
Clone the repo
git clone --depth 1 https://github.com/hookdeck/webhook-skills

Made for: Claude Code, Codex.

Per session 43 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,842 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 84% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 2d ago against content hash 3a0ac4e8c31e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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.

The scan reads SKILL.md. This mod also ships 7 executable files (examples/express/src/index.js, examples/express/test/webhook.test.js, examples/fastapi/main.py, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

Origin

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.

skills/gitlab-webhooks/SKILL.md · 186 lines

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 });
  }
);

Read the full file on GitHub · 186 lines

Changes

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.

  1. 2d ago First seen · 186 lines · 43 tokens per session scan A 3a0ac4e8c31e

Subscribe to this mod's changes

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.

Related

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.

GanyuanRan/Aegis · 35 tokens

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.

cwinvestments/memstack · 65 tokens

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…

waybarrios/opencode-power-pack · 61 tokens

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…

open-mercato/open-mercato · 134 tokens

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.

thiientv/godmode · 56 tokens

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.

iamtouchskyer/memex · 38 tokens