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/hookdeck-cli/hookdeck-cli-releasenpx skills add hookdeck/hookdeck-cli --skill hookdeck-cli-releasegit clone --depth 1 https://github.com/hookdeck/hookdeck-cliWhat 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.00104 | $0.03516 |
| Opus 5 | $0.00052 | $0.01758 |
| Sonnet 5 | $0.00021 | $0.00703 |
| Haiku 4.5 | $0.00010 | $0.00352 |
Grade A, and why
hookdeck-cli-release 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.
How it starts
The opening of the file, as written. The whole thing — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hookdeck CLI — release workflow
Canonical documentation
Follow README.md § Releasing for human-oriented steps (GitHub UI alternative, install commands for beta/stable).
Agents: perform the publish step with the GitHub CLI (gh) — see Publish with GitHub CLI (gh) below (temp notes file → gh release create → remove temp file).
This skill adds how automation works, release note expectations, and a research loop for drafting notes.
Agent checklist (end-to-end)
Follow in order. Treat items with gate as blocking unless the maintainer explicitly overrides.
- Release shape: GA from
mainvs beta frommainvs beta from feature branch — matches README § Releasing and maintainer intent. -
PREV_TAG/NEW_TAG: Confirmed (or proposed and agreed); baseline tag is correct for the line of development (e.g. last GA vs beta series). - Change set: Reviewed
git log PREV_TAG..HEAD(and diff if needed); changes grouped for user-facing release notes (see Research loop). - SemVer gate: Proposed
NEW_TAGmatches minimum MAJOR/MINOR/PATCH for the delta (see SemVer: validate the proposed version). Stop and realign if under-bumped. - Release notes: Draft complete (see Drafting release notes and references/release-notes-template.md); includes Full Changelog compare link; contributor shout-outs only when warranted (see that section).
- CI gate: Latest commit on the target branch has green GitHub checks (mandatory for GA on
main; required for betas on the branch being tagged). - Approval: Maintainer signed off on tag name, notes, and branch — no unilateral surprise tags.
- Publish: Write notes to a temporary file, run
gh release create(see Publish with GitHub CLI (gh)), thenrmthe temp file. Use--prereleasefor betas. (Humans may still use the GitHub UI per README.) - Post-publish (optional): Confirm the
releaseworkflow in Actions completed successfully for the new tag.
What ships with it
1 file 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.
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 · 192 lines · 104 tokens per session scan A 01295ee03ff1
hookdeck-cli-release is a skill published in the GitHub repository hookdeck/hookdeck-cli (360 stars, last pushed 8d ago), licensed Apache-2.0. It adds 104 tokens to every session and 3,516 once invoked, about $0.0005 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-30.
Other skills, from other repositories
calendar-scheduling
Use when a product needs a booking surface — a pick-a-slot page, a Cal.com/Calendly embed, or real availability plus the confirmed meeting written to Google/Outlook — or when fixing double-booking, DST drift, or orphaned reschedule events. NOT calendar CRUD with no booking surface (that is google-workspace), NOT the…
portr-cli
Use when an AI agent or harness needs to operate the Portr CLI: authenticate a client, add users to teams, create HTTP/WebSocket/TCP/stub tunnels, run config-defined tunnels, inspect request logs, replay captured requests, or control tunnels through the local app-server API. This skill is compatible with Claude Code…
frontmcp-channels
Use when pushing real-time notifications or events into Claude Code (or another MCP client) sessions, or building two-way chat bridges. Covers channel source types: incoming webhooks (such as GitHub), app error events, agent-completion and job-completion alerts, service connectors, file watchers, and replay buffers…
xquik
Xquik X data automation API - Use REST or MCP for tweet search, user lookup, follower exports, media downloads, monitors, webhooks, giveaway draws, and confirmation-gated X actions.
pipefy-members-email-webhooks
Use this skill when the user wants to manage pipe membership, send or read card inbox emails, use email templates, or manage webhooks. Covers 12 MCP tools.
svix-sending-webhooks
Everything for working with Svix webhooks: first-time setup (API key, SDK install, first message), Dispatch (sending webhooks to your customers), Ingest (receiving third-party webhooks), Applications, Channels, customer UIDs, idempotency, App Portal embedding, operational webhooks, the Svix CLI, and — only when the…