quo-webhooks

quo-webhooks is a skill for Claude Code, Codex from hookdeck/webhook-skills. It costs 167 tokens per session (5,359 once invoked), scanned A, original, MIT.

A guide for receiving and verifying Quo webhooks. Quo, formerly OpenPhone, is a business phone service that sends HTTP notifications about calls, messages, contacts, and tasks to an application.

In plain words
What is it for?
Use it to build or debug a webhook endpoint, verify request signatures, and handle events such as received messages, completed calls, summaries, and transcripts.
Why use it?
It helps prevent forged or misread event requests by explaining Quo's signature schemes and the differences between its current and legacy APIs.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to build or debug a webhook endpoint, verify request signatures, and handle events such as received messages, completed calls, summaries, and transcripts.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/hookdeck/webhook-skills/quo-webhooks
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.

Any agent
npx skills add hookdeck/webhook-skills --skill quo-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 quo-webhooks — /plugin install quo-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 quo-webhooks

README.md
[![agentmods](https://agentmods.dev/badge/skills/hookdeck/webhook-skills/quo-webhooks/github.svg)](https://agentmods.dev/skills/hookdeck/webhook-skills/quo-webhooks)
Your own site
<a href="https://agentmods.dev/skills/hookdeck/webhook-skills/quo-webhooks"><img src="https://agentmods.dev/badge/skills/hookdeck/webhook-skills/quo-webhooks/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for quo-webhooks

Your own site · 80×15
<a href="https://agentmods.dev/skills/hookdeck/webhook-skills/quo-webhooks"><img src="https://agentmods.dev/badge/skills/hookdeck/webhook-skills/quo-webhooks.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 167 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 5,359 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.
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.00167 $0.05359
Opus 5.5 $0.00067 $0.02144
Sonnet 5.5 $0.00033 $0.01072
Haiku 4.5 $0.00017 $0.00536

Measured 23d ago against content hash f9ee08e874ff, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

quo-webhooks scanned grade A with 1 finding 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 23d 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl -X POST https://api.quo.com/webhooks \
skills/quo-webhooks/SKILL.md · 378 lines

How it starts

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

Quo Webhooks

Quo (quo.com) is a business phone / VoIP platform. It sends webhooks for calls, messages, contacts and tasks.

Quo is the platform formerly known as OpenPhone. The support docs say so verbatim: "Send real-time notifications of Quo, formerly OpenPhone, events to your applications". The rebrand is why the legacy signature header is still called openphone-signature, and why older community material talks about OpenPhone webhooks. API host is https://api.quo.com; docs live at www.quo.com/docs and support.quo.com.

Not Quoter. Quoter (help.quoter.com) is an unrelated CPQ / sales-quoting company with an MD5-based hash form field (not a header). Quo uses HMAC-SHA256. Two different companies, two entirely different signing schemes. Also not Quora, not the Quo card/loyalty app, and not Twilio.

When to Use This Skill

  • How do I receive Quo (OpenPhone) webhooks?
  • How do I verify a Quo webhook signature?
  • Why is my webhook-signature / openphone-signature verification failing?
  • How do I handle message.received, call.completed, or call.summary.completed events?
  • What is the difference between data.resource and data.object in a Quo payload?
  • How do I deduplicate Quo webhook deliveries?
  • Does Quo send a validation / challenge request when I add an endpoint?

Two Generations, Two Signature Schemes

This is the first thing to get right. Which scheme an endpoint receives is decided by how the webhook subscription was created, not by anything you configure on your server. A handler that may receive both must implement both.

Scheme A — current Scheme B — legacy
Created via POST /webhooks with Quo-Api-Version: 2026-03-30 legacy /v1/webhooks/messages, /v1/webhooks/calls, …
Header(s) webhook-id, webhook-timestamp, webhook-signature openphone-signature (single header)
Header format webhook-signature: v1,<base64> v1,<base64> (space-separated) hmac;1;1639710054089;mw1K4fv…= (semicolon-separated, 4 fields)
Signed content {webhook-id}.{webhook-timestamp}.{raw-body} {timestamp}.{raw-body}
Timestamp unit UNIX seconds UNIX milliseconds (inferred — see below)
Secret key from POST /webhooks, whsec_<base64> app → webhook → ⋯ → "Reveal signing secret", bare base64
Envelope data.resource / data.context / data.links data.object
apiVersion "2026-03-30" "v2" ("v3" for AI events)

Read the full file on GitHub · 378 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. 23d ago First seen · 378 lines · 167 tokens per session scan A f9ee08e874ff

Subscribe to this mod's changes

quo-webhooks is a skill published in the GitHub repository hookdeck/webhook-skills (92 stars, last pushed today), licensed MIT. It adds 167 tokens to every session and 5,359 once invoked, about $0.0007 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-24.

Related

Other skills, from other repositories

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

systematic-debugging

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

obra/superpowers · 21 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

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens