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/agent-skills/event-gatewaynpx skills add hookdeck/agent-skills --skill event-gatewaygit clone --depth 1 https://github.com/hookdeck/agent-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/agent-skills/event-gateway)<a href="https://agentmods.dev/skills/hookdeck/agent-skills/event-gateway"><img src="https://agentmods.dev/badge/skills/hookdeck/agent-skills/event-gateway.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.00137 | $0.04476 |
| Opus 5 | $0.00068 | $0.02238 |
| Sonnet 5 | $0.00027 | $0.00895 |
| Haiku 4.5 | $0.00014 | $0.00448 |
Grade A, and why
event-gateway 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 200 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hookdeck Event Gateway
The Event Gateway receives, routes, processes, and delivers webhooks and events. The core model: a Source (ingestion endpoint with a unique https://hkdk.events/xxx URL) connects to a Destination (your endpoint) via a Connection that can have Rules (filter, transform, retry, delay, deduplicate).
Documentation
Always reference Hookdeck docs as the source of truth. See references/referencing-docs.md for how to fetch docs as markdown.
Authenticating without a browser (agents, CI, sandboxes)
hookdeck login needs a browser and hookdeck login -i needs a TTY. Use
hookdeck ci, which reads HOOKDECK_API_KEY from the environment, before any
other CLI command:
hookdeck ci # exchanges the Project API key for CLI credentials
hookdeck whoami # confirm the expected organization and project
Without this the CLI creates a temporary guest account and keeps going, so commands appear to succeed against a project the user cannot see. See references/cli-workflows.md#non-interactive-environments.
CLI command model
- Prefer
hookdeck gateway ...for Event Gateway resource management, querying, and analysis. - Keep root commands for shell/context workflows (
hookdeck login,hookdeck whoami,hookdeck listen,hookdeck project ...). - Root
hookdeck connection ...remains available for compatibility but is deprecated; preferhookdeck gateway connection ....
Hookdeck CLI prerequisite
Whenever you show hookdeck … commands in answers, READMEs, or runbooks, tell the user the Hookdeck CLI must be installed first the first time those commands appear—even for no-account flows that go straight to hookdeck listen. Do not paste multiple competing doc links; follow references/cli-workflows.md#hookdeck-cli-prerequisite for standard wording, install examples, the official install URL, and the in-repo install section.
What ships with it
31 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 222 B
- examples/express/package.json 392 B
- examples/express/README.md 1.0 KB
- examples/express/src/index.js 2.4 KB runs code
- examples/express/test/webhook.test.js 4.3 KB runs code
- examples/fastapi/.env.example 168 B
- examples/fastapi/main.py 1.9 KB runs code
- examples/fastapi/README.md 1.0 KB
- examples/fastapi/requirements.txt 82 B
- examples/fastapi/test_webhook.py 4.5 KB runs code
- examples/nextjs/.env.example 168 B
- examples/nextjs/app/webhooks/route.ts 1.8 KB runs code
- examples/nextjs/package.json 501 B
- examples/nextjs/README.md 1.0 KB
- examples/nextjs/test/webhook.test.ts 4.0 KB runs code
- examples/nextjs/vitest.config.ts 140 B runs code
- references/01-setup.md 7.3 KB
- references/02-scaffold.md 8.7 KB
- references/03-listen.md 5.1 KB
- references/04-iterate.md 4.7 KB
- references/api-patterns.md 4.4 KB
- references/authentication.md 5.6 KB
- references/cli-workflows.md 14 KB
- references/connection-architecture.md 4.0 KB
- references/connection-rules.md 6.3 KB
- references/monitoring-debugging.md 11 KB
- references/provider-webhooks-checklist.md 5.6 KB
- references/referencing-docs.md 4.1 KB
- references/terminology-gotchas.md 4.5 KB
- references/verification-code.md 7.9 KB
- tile.json 238 B
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.
- 4d ago First seen · 200 lines · 137 tokens per session scan A 59c2202ad2f1
event-gateway is a skill published in the GitHub repository hookdeck/agent-skills (5 stars, last pushed 16d ago), licensed MIT. It adds 137 tokens to every session and 4,476 once invoked, about $0.0007 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-08-31.
Other skills, from other repositories
mcporter
List, auth, and call MCP servers/tools from the terminal.
article-writing
Write articles, guides, blog posts, tutorials, newsletter issues, and other long-form content in a distinctive voice derived from supplied examples or brand guidance. Use when the user wants polished written content longer than a paragraph, especially when voice consistency, structure, and credibility matter.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
complete-partial-pr
Evaluate and complete an issue or PR where the submitted patch fixes only a narrow symptom of the reported pain point. Use when a contribution may miss adjacent integration surfaces, provider/spec semantics, roundtrip behavior, tests, docs, or historical maintainer decisions.
deploy-docker-compose
Run the Omnigent server as a Docker compose stack (server + Postgres) on any Docker host — your laptop, a VPS, EC2 by hand, or as the base layer of any container-platform deploy. Invoke when the user wants to build the image, bring up the compose stack, debug the stack on a host they already have, or extend the stack…
mapping-to-snomed
Maps clinical concept spans extracted by OpenMed to SNOMED CT concepts through a USER-SUPPLIED terminology server (the user's own Ontoserver, Snowstorm, or UMLS/UTS), never a bundled vocabulary. Use when the user wants to code findings, disorders, procedures, body structures, or substances to SNOMED CT, run an ECL…