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/dodopayments/dodo-agent-plugin/webhook-integrationnpx skills add dodopayments/dodo-agent-plugin --skill webhook-integrationgit clone --depth 1 https://github.com/dodopayments/dodo-agent-pluginWrote 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/dodopayments/dodo-agent-plugin/webhook-integration)<a href="https://agentmods.dev/skills/dodopayments/dodo-agent-plugin/webhook-integration"><img src="https://agentmods.dev/badge/skills/dodopayments/dodo-agent-plugin/webhook-integration.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.00024 | $0.06040 |
| Opus 5 | $0.00012 | $0.03020 |
| Sonnet 5 | $0.00005 | $0.01208 |
| Haiku 4.5 | $0.00002 | $0.00604 |
Grade A, and why
webhook-integration 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.
This is a copy
100% identical to webhook-integration — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 728 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dodo Payments Webhook Integration
Webhooks deliver real-time notifications when payment events occur. Use them to automate workflows, update databases, send confirmations, and keep your systems in sync.
When to use this skill
- Setting up a webhook endpoint to receive payment, subscription, or refund events
- Implementing signature verification to ensure webhook authenticity
- Handling specific event types (payment succeeded, subscription renewed, etc.)
- Testing webhooks locally during development
- Ensuring idempotent webhook processing to handle retries
Core Concepts
Webhook: An HTTP POST request sent by Dodo to your endpoint when an event occurs.
Signature verification: Cryptographic proof that a webhook came from Dodo, not an attacker. Required for production.
Idempotency: Processing the same webhook multiple times produces the same result. Use the webhook-id header to detect and skip duplicates.
Raw body: The exact bytes received from Dodo, before parsing. Required for signature verification.
Setup: Creating a Webhook Endpoint
1. Create the endpoint in the dashboard
- Go to Developer → Webhooks
- Click Create Webhook
- Enter your endpoint URL (must be HTTPS in production)
- Select the events you want to receive
- Copy the signing secret
2. Store the signing secret
export DODO_PAYMENTS_WEBHOOK_KEY=whsec_...
The SDK reads this automatically. You can also pass it explicitly when initializing the client.
Webhook Headers and Payload
Every webhook request includes three required headers (all lowercase, hyphenated):
| Header | Example | Purpose |
|---|---|---|
webhook-id |
evt_abc123 |
Unique identifier for this webhook delivery |
webhook-signature |
v1,base64_signature_here |
HMAC-SHA256 signature for verification |
webhook-timestamp |
1704067200 |
Unix timestamp (seconds) when the event was sent |
The request body is JSON:
{
"business_id": "bus_xxxxx",
"type": "payment.succeeded",
"timestamp": "2024-01-01T12:00:00Z",
"data": {
"payload_type": "Payment",
"payment_id": "pay_xxxxx",
"status": "succeeded",
"total_amount": 2999,
"currency": "USD",
"customer": {
"customer_id": "cus_xxxxx",
"email": "[email protected]",
"name": "John Doe"
}
}
}
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 · 728 lines · 24 tokens per session scan A 883a651b110e
webhook-integration is a skill published in the GitHub repository dodopayments/dodo-agent-plugin (6 stars, last pushed 10d ago), licensed MIT. It adds 24 tokens to every session and 6,040 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to webhook-integration, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
cmux-billing
Stripe checkout, pricing, subscription, Pro plan, webhook, and entitlement runbook for cmux billing work. Use when editing or debugging billing, pricing, Stripe Checkout, subscription recording, Pro plan status, webhooks, entitlement metadata, or pricing dev/prod tooling.
opencode-ensemble
Use when coordinating multiple coding agents, delegating independent software work, managing OpenCode Ensemble teams, choosing teammate roles or models, reviewing teammate output, or deciding whether parallel execution is appropriate.
cli-review
Runs a Greptile CLI review for the current local branch, installing or authenticating the CLI when needed, then summarizes JSON findings for the user. Use when the user wants Greptile feedback before opening a PR, outside a hosted PR review flow, or directly from a local checkout.
ce:plan
Create structured plans for any multi-step task -- software features, research workflows, events, study plans, or any goal that benefits from structured breakdown. Also deepen existing plans with interactive review of sub-agent findings. Use for plan creation when the user says 'plan this', 'create a plan', 'write a…
ce:review
Structured code review using tiered persona agents, confidence-gated findings, and a merge/dedup pipeline. Use when reviewing code changes before creating a PR.
ce:compound-refresh
Refresh stale or drifting learnings and pattern docs in docs/solutions/ by reviewing, updating, consolidating, replacing, or deleting them against the current codebase. Use after refactors, migrations, dependency upgrades, or when a retrieved learning feels outdated or wrong. Also use when reviewing docs/solutions/…