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/webhook-co/webhook/infra-deploy-runbooknpx skills add webhook-co/webhook --skill infra-deploy-runbookgit clone --depth 1 https://github.com/webhook-co/webhookWrote 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/webhook-co/webhook/infra-deploy-runbook)<a href="https://agentmods.dev/skills/webhook-co/webhook/infra-deploy-runbook"><img src="https://agentmods.dev/badge/skills/webhook-co/webhook/infra-deploy-runbook.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.00047 | $0.00489 |
| Opus 5 | $0.00023 | $0.00244 |
| Sonnet 5 | $0.00009 | $0.00098 |
| Haiku 4.5 | $0.00005 | $0.00049 |
Grade A, and why
infra-deploy-runbook 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.
What it actually says
Infra deploy runbook
Operate the Cloudflare-forward stack (Workers + Durable Objects, Neon via Hyperdrive, R2, KV) and the container-delivery lane behind the seam.
Before any deploy
- Confirm the change is reproducible from
infra/and carries no secrets or account/zone IDs. - Run a plan/dry-run first (
wrangler deploy --dry-run, IaC plan). Read the diff. - Identify blast radius: does it touch DNS/routing for
webhook.coorwbhk.my, drop/recreate resources, or rotate production secrets? If yes → stop and get human review.
Deploy order (per service)
- Apply additive changes first (new bindings, new DO classes, expand-phase migrations).
- Deploy the Worker/service; verify health + OpenTelemetry traces before shifting traffic.
- Watch error rate and delivery latency; keep the previous version ready to roll back.
Guardrails (non-negotiable)
- Default new compute to Workers / DO. Don't reintroduce rejected stack alternatives without an ADR.
- Preserve the container-delivery seam — never couple the engine to a specific delivery backend.
- Keep
wbhk.myingestion cookieless, no-CORS, path-token routed,404for unknown tokens. - Secrets via
wrangler secret/ secret store only. No literals, no account IDs in the repo.
Rollback
- Workers: redeploy the prior version. DO: ensure schema is backward-compatible before cutover so rollback is safe. Migrations: only ship the contract phase once rollback is no longer needed.
Progressive disclosure
Put environment-specific checklists, binding maps, and step-by-step rollback drills in
references/ (e.g. references/rollback.md) and link them here rather than inlining detail.
references/www-static-assets.md— deployapps/wwwto www.webhook.co (assets-only Worker,_headers, apex→www redirect, HSTS, GitHub Actions CD).
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.
- 3d ago First seen · 43 lines · 47 tokens per session scan A 90b0af0a9b1c
infra-deploy-runbook is a skill published in the GitHub repository webhook-co/webhook (0 stars, last pushed 9d ago), licensed Apache-2.0. It adds 47 tokens to every session and 489 once invoked, about $0.0002 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
cloudflare-deploy
Deploy applications and infrastructure to Cloudflare using Workers, Pages, and related platform services. Use when the user asks to deploy, host, publish, or set up a project on Cloudflare.
cloudflare
Comprehensive Cloudflare platform skill covering Workers, Pages, storage (KV, D1, R2), AI (Workers AI, Vectorize, Agents SDK), networking (Tunnel, Spectrum), security (WAF, DDoS), and infrastructure-as-code (Terraform, Pulumi). Use for any Cloudflare development task. Biases towards retrieval from Cloudflare docs over…
wrangler
Cloudflare Workers CLI for deploying, developing, and managing Workers, KV, R2, D1, Vectorize, Hyperdrive, Workers AI, Containers, Queues, Workflows, Pipelines, and Secrets Store. Load before running wrangler commands to ensure correct syntax and best practices. Biases towards retrieval from Cloudflare docs over…
workers-best-practices
Reviews and authors Cloudflare Workers code against production best practices. Load when writing new Workers, reviewing Worker code, configuring wrangler.jsonc, or checking for common Workers anti-patterns (streaming, floating promises, global state, secrets, bindings, observability). Biases towards retrieval from…
add-provider
Add a new storage or service provider to the core package. Use when implementing a new backend for StorageService (e.g., a new database) or a new service provider (e.g., a new LLM backend).
add-export
Add a new subpath export to the @cyanheads/mcp-ts-core package. Use when creating a new public API surface that consumers import from a dedicated subpath (e.g., @cyanheads/mcp-ts-core/newutil).