agentmods.dev

webhook

webhook is a command for Claude Code from doncheli/don-cheli-sdd. It costs 89 tokens per session (1,900 once invoked), scanned A, original, Apache-2.0.

A webhook configuration command for connecting external services to automated commands. A webhook is an event sent from one system to another when something happens, such as opening a pull request or receiving an alert.

In plain words
What is it for?
Use it to add, remove, test, list, monitor, log, or export event-triggered automations, including CI failures and pull-request events.
Why use it?
It removes the need to start certain responses manually when events occur in GitHub, Slack, Linear, or PagerDuty.

Command for Claude Code

Written for Claude Code: installed under .claude/.

Part of the don-cheli-sdd plugin — 28 skills, 115 commands, 1 agent shipped together

not rated 57 26d ago A scan 89 tokens original Apache-2.0
View the source file doncheli/don-cheli-sdd doncheli.tv
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 commands/doncheli/don-cheli-sdd/webhook
Clone the repo
git clone --depth 1 https://github.com/doncheli/don-cheli-sdd

Made for: Claude Code.

Or install don-cheli-sdd, the plugin that ships this one along with the rest of its 28 skills, 115 commands, 1 agent.

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 webhook

README.md
[![agentmods](https://agentmods.dev/badge/commands/doncheli/don-cheli-sdd/webhook.svg)](https://agentmods.dev/commands/doncheli/don-cheli-sdd/webhook)
Your own site
<a href="https://agentmods.dev/commands/doncheli/don-cheli-sdd/webhook"><img src="https://agentmods.dev/badge/commands/doncheli/don-cheli-sdd/webhook.svg" alt="Measured on agentmods" height="20"></a>
Per session 89 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,900 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.00089 $0.01900
Opus 5 $0.00044 $0.00950
Sonnet 5 $0.00018 $0.00380
Haiku 4.5 $0.00009 $0.00190

Measured 3d ago against content hash 64ca8aaaa92b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

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

scripts/.claude/commands/dc/webhook.md · 203 lines

How it starts

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

/dc:webhook

Objetivo

Integrar Don Cheli con sistemas externos a través de webhooks y eventos. Configurar reacciones automáticas: al abrir un PR en GitHub ejecutar /dc:revisar, al crear un issue en Linear ejecutar /dc:comenzar, al recibir alerta en PagerDuty ejecutar diagnóstico. La configuración se almacena en .dc/webhooks.yaml.

Uso

/dc:webhook --listar                          # Ver todos los webhooks configurados
/dc:webhook --agregar github:pr_opened        # Configurar nuevo evento
/dc:webhook --eliminar wh-003                 # Eliminar configuración por ID
/dc:webhook --probar wh-001                   # Enviar evento de prueba
/dc:webhook --log                             # Ver log de eventos recibidos
/dc:webhook --estado                          # Dashboard de salud de webhooks
/dc:webhook --exportar                        # Exportar config para compartir con equipo

Fuentes de Eventos Soportadas

Fuente Eventos Disponibles
GitHub pr_opened, pr_merged, pr_review_requested, push, issue_created, issue_closed, ci_failed
Slack slash_command, mention, reaction_added, message_in_channel
Linear issue_created, issue_updated, issue_assigned, cycle_started
PagerDuty incident_triggered, incident_resolved, alert_fired
HTTP custom POST /webhook/<id> — payload arbitrario

Comportamiento

  1. Cargar configuración desde .dc/webhooks.yaml

  2. Para --agregar:

    • Solicitar fuente, evento, filtros opcionales y comando a ejecutar
    • Generar ID único (wh-XXX)
    • Generar URL del endpoint si aplica
    • Mostrar instrucciones de configuración en la fuente externa
    • Guardar en .dc/webhooks.yaml

  3. Para --probar:

    • Enviar payload de prueba al handler del webhook
    • Ejecutar comando configurado en modo dry-run
    • Reportar resultado y tiempo de ejecución

  4. Para --log:

    • Leer .dc/webhook-log.jsonl
    • Mostrar últimos 50 eventos con estado (procesado/fallido/ignorado)

Read the full file on GitHub · 203 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. 3d ago First seen · 203 lines · 89 tokens per session scan A 64ca8aaaa92b

Subscribe to this mod's changes

webhook is a command published in the GitHub repository doncheli/don-cheli-sdd (57 stars, last pushed 26d ago), licensed Apache-2.0. It adds 89 tokens to every session and 1,900 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.

CI and CDDevOps and cloudGit and workflowagentic-codingai-agentsai-codingai-developmentanthropic-skillsclaude
Related

Other commands, from other repositories

reapply-patches

Reapply local modifications after a PBR update.

SienkLogic/plan-build-run · 9 tokens

forensics

Post-mortem investigation for failed or stuck workflows. Analyzes git history and planning artifacts.

SienkLogic/plan-build-run · 20 tokens

release

Generate or update changelog and release notes from project history.

SienkLogic/plan-build-run · 12 tokens

audit-fix

Run audit, prioritize findings, auto-fix via quick tasks, test, and commit.

SienkLogic/plan-build-run · 18 tokens

build

Execute all plans in a phase. Spawns agents to build in parallel, commits atomically.

SienkLogic/plan-build-run · 19 tokens

quick

Execute an ad-hoc task with atomic commits. Skips full plan/review.

SienkLogic/plan-build-run · 17 tokens