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/webhook-skills/razorpay-webhooksnpx skills add hookdeck/webhook-skills --skill razorpay-webhooksgit clone --depth 1 https://github.com/hookdeck/webhook-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/webhook-skills/razorpay-webhooks)<a href="https://agentmods.dev/skills/hookdeck/webhook-skills/razorpay-webhooks"><img src="https://agentmods.dev/badge/skills/hookdeck/webhook-skills/razorpay-webhooks.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.00059 | $0.01455 |
| Opus 5 | $0.00030 | $0.00727 |
| Sonnet 5 | $0.00012 | $0.00291 |
| Haiku 4.5 | $0.00006 | $0.00145 |
Grade A, and why
razorpay-webhooks 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 yesterday.
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
86% identical to adyen-webhooks — 152 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Razorpay Webhooks
Razorpay is an India-focused payments platform. It notifies your application of payment lifecycle events (orders, payments, refunds, subscriptions, settlements, disputes) by sending an HTTP POST webhook with a JSON payload to your endpoint.
When to Use This Skill
- How do I receive Razorpay webhooks?
- How do I verify the
X-Razorpay-Signatureheader? - Why is my Razorpay webhook signature verification failing?
- How do I handle
payment.captured,order.paid, orsubscription.chargedevents? - Understanding Razorpay event types and payload structure
Verification (core)
Razorpay signs each webhook with HMAC-SHA256 over the raw request body,
hex-encoded, in the X-Razorpay-Signature header. The key is the webhook
secret you set in the dashboard (not your API key). Verify the raw body —
do not JSON.parse before verifying.
The official razorpay Node SDK exposes a static helper:
const Razorpay = require('razorpay');
// rawBody: the raw HTTP body as a string/Buffer (NOT parsed JSON)
// signature: value of the X-Razorpay-Signature header
// secret: RAZORPAY_WEBHOOK_SECRET from the dashboard webhook config
const isValid = Razorpay.validateWebhookSignature(rawBody, signature, secret);
// returns true/false
No Node SDK (e.g. Python/FastAPI)? Compute it manually with a timing-safe compare:
import hmac, hashlib
expected = hmac.new(secret.encode(), raw_body, hashlib.sha256).hexdigest()
is_valid = hmac.compare_digest(expected, signature_header)
For complete handlers with route wiring, event dispatch, and tests, see:
Common Event Types
The event type is in the JSON body's event field (not a header).
| Event | Triggered When |
|---|---|
payment.authorized |
Payment authorized but not yet captured |
payment.captured |
Payment successfully captured |
payment.failed |
Payment attempt failed |
order.paid |
An order is fully paid |
refund.processed |
A refund has been processed |
subscription.charged |
A subscription charge succeeded |
What ships with it
20 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 262 B
- examples/express/package.json 398 B
- examples/express/README.md 1.6 KB
- examples/express/src/index.js 4.1 KB runs code
- examples/express/test/webhook.test.js 6.1 KB runs code
- examples/fastapi/.env.example 193 B
- examples/fastapi/main.py 3.4 KB runs code
- examples/fastapi/README.md 1.7 KB
- examples/fastapi/requirements.txt 82 B
- examples/fastapi/test_webhook.py 5.3 KB runs code
- examples/nextjs/.env.example 193 B
- examples/nextjs/app/webhooks/razorpay/route.ts 3.3 KB runs code
- examples/nextjs/package.json 510 B
- examples/nextjs/README.md 1.6 KB
- examples/nextjs/test/webhook.test.ts 5.0 KB runs code
- examples/nextjs/tsconfig.json 562 B
- examples/nextjs/vitest.config.ts 140 B runs code
- references/overview.md 3.2 KB
- references/setup.md 2.6 KB
- references/verification.md 4.5 KB
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.
- yesterday First seen · 127 lines · 59 tokens per session scan A 5763fb8c6390
razorpay-webhooks is a skill published in the GitHub repository hookdeck/webhook-skills (84 stars, last pushed yesterday), licensed MIT. It adds 59 tokens to every session and 1,455 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to adyen-webhooks, differing in 152 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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.
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…