vercel-log-drains-webhooks

vercel-log-drains-webhooks is a skill for Claude Code, Codex from hookdeck/webhook-skills. It costs 74 tokens per session (1,852 once invoked), scanned A, original, MIT.

Instructions for receiving and verifying Vercel Log Drains. A log drain forwards deployment and runtime logs from Vercel to an HTTPS endpoint.

In plain words
What is it for?
They are for collecting logs from Vercel functions, edge services, builds, firewalls, and redirects.
Why use it?
They help you accept logs safely, complete Vercel's endpoint check, and correctly read batches of log entries.

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/vercel-log-drains-webhooks
Any agent
npx skills add hookdeck/webhook-skills --skill vercel-log-drains-webhooks
Clone the repo
git clone --depth 1 https://github.com/hookdeck/webhook-skills

Made for: Claude Code, Codex.

Its marketplace also offers this one on its own, as the plugin vercel-log-drains-webhooks/plugin install vercel-log-drains-webhooks after adding the marketplace above.

Wrote 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.

agentmods badge for vercel-log-drains-webhooks

README.md
[![agentmods](https://agentmods.dev/badge/skills/hookdeck/webhook-skills/vercel-log-drains-webhooks.svg)](https://agentmods.dev/skills/hookdeck/webhook-skills/vercel-log-drains-webhooks)
Your own site
<a href="https://agentmods.dev/skills/hookdeck/webhook-skills/vercel-log-drains-webhooks"><img src="https://agentmods.dev/badge/skills/hookdeck/webhook-skills/vercel-log-drains-webhooks.svg" alt="Measured on agentmods" height="20"></a>
Per session 74 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,852 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found 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.1 $0.00074 $0.01852
Opus 5 $0.00037 $0.00926
Sonnet 5 $0.00015 $0.00370
Haiku 4.5 $0.00007 $0.00185

Measured 2d ago against content hash 0e93ab69c1d3, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, from the pricing page.

Security

Grade A, and why

vercel-log-drains-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.

skills/vercel-log-drains-webhooks/SKILL.md · 169 lines

How it starts

The opening of the file, as written. The whole thing — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Vercel Log Drains Webhooks

Vercel Log Drains forward deployment logs to any HTTPS endpoint you configure. These are HTTP log-drain deliveries (not "Vercel webhooks" and not Standard Webhooks): Vercel POSTs batches of log entries and signs the raw body with HMAC-SHA1.

When to Use This Skill

  • How do I receive Vercel Log Drains?
  • How do I verify the x-vercel-signature header?
  • How do I complete the x-vercel-verify endpoint handshake?
  • Why is my Vercel log drain signature verification failing?
  • How do I parse batched log entries (JSON array or NDJSON)?
  • How do I handle logs from lambda, edge, build, or firewall sources?

Verification (core)

Vercel signs the raw request body with HMAC-SHA1 keyed on your drain's signature secret and sends the hex digest in the x-vercel-signature header (the raw digest — no sha1= prefix). Use the raw body (do not re-serialize), and compare timing-safe.

Node:

const crypto = require('crypto');

function verify(rawBody, signatureHeader, secret) {
  if (!signatureHeader) return false;
  const expected = crypto.createHmac('sha1', secret).update(rawBody).digest('hex');
  try {
    return crypto.timingSafeEqual(
      Buffer.from(signatureHeader, 'hex'),
      Buffer.from(expected, 'hex')
    );
  } catch {
    return false; // wrong length / not hex
  }
}

Python:

import hmac, hashlib

def verify(raw_body: bytes, signature_header: str, secret: str) -> bool:
    if not signature_header:
        return False
    expected = hmac.new(secret.encode(), raw_body, hashlib.sha1).hexdigest()
    return hmac.compare_digest(signature_header, expected)

Endpoint handshake (x-vercel-verify)

When a drain is created or tested, Vercel sends an unsigned probe request. Your endpoint must respond 200 OK with an x-vercel-verify response header echoing the verification token shown in the dashboard. Because the probe is unsigned, treat a request with no x-vercel-signature as the handshake: return 200 with the verify header and do not process logs. Signed deliveries then carry x-vercel-signature; reject those with an invalid signature (403).

Read the full file on GitHub · 169 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 · 169 lines · 74 tokens per session scan A 0e93ab69c1d3

Subscribe to this mod's changes

vercel-log-drains-webhooks is a skill published in the GitHub repository hookdeck/webhook-skills (84 stars, last pushed 2d ago), licensed MIT. It adds 74 tokens to every session and 1,852 once invoked, about $0.0004 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens