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/furkangonel/cowrangler/webhook-subscriptionsnpx skills add furkangonel/cowrangler --skill webhook-subscriptionsgit clone --depth 1 https://github.com/furkangonel/cowranglerWrote 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/furkangonel/cowrangler/webhook-subscriptions)<a href="https://agentmods.dev/skills/furkangonel/cowrangler/webhook-subscriptions"><img src="https://agentmods.dev/badge/skills/furkangonel/cowrangler/webhook-subscriptions.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.00018 | $0.02310 |
| Opus 5 | $0.00009 | $0.01155 |
| Sonnet 5 | $0.00004 | $0.00462 |
| Haiku 4.5 | $0.00002 | $0.00231 |
Grade A, and why
webhook-subscriptions 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 4d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
const response = await fetch(url, { How it starts
The opening of the file, as written. The whole thing — 315 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Webhook Subscriptions SOP
When to Use
- User wants to receive events from an external service (Stripe, GitHub, Shopify, Twilio, etc.)
- User wants to send webhooks from their own service to subscribers
- User is debugging why webhooks aren't being received or processed
- User wants to validate webhook security or handle retries
Part 1 — Receiving Webhooks
Minimal Express.js Handler
import express from "express";
import crypto from "crypto";
const app = express();
// IMPORTANT: use raw body for signature validation, not parsed JSON
app.post(
"/webhooks/stripe",
express.raw({ type: "application/json" }),
async (req, res) => {
// 1. Validate signature first — reject early if invalid
const signature = req.headers["stripe-signature"] as string;
const isValid = validateStripeSignature(req.body, signature);
if (!isValid) {
console.warn("Invalid webhook signature", { signature });
return res.status(400).json({ error: "Invalid signature" });
}
// 2. Parse the payload
const event = JSON.parse(req.body.toString());
// 3. Respond 200 immediately — do not wait for processing
res.status(200).json({ received: true });
// 4. Process asynchronously (after responding)
await processEvent(event).catch((err) => {
console.error("Webhook processing failed", { eventId: event.id, err });
});
}
);
Why respond 200 immediately?
Most webhook providers retry on any non-2xx response or on timeout (typically 10–30 seconds). Long-running processing will cause unnecessary retries. Always acknowledge first, process after.
Part 2 — Signature Validation (HMAC)
Generic HMAC-SHA256 Validation
function validateWebhookSignature(
payload: Buffer,
receivedSig: string,
secret: string
): boolean {
const expectedSig = crypto
.createHmac("sha256", secret)
.update(payload)
.digest("hex");
// Constant-time comparison to prevent timing attacks
return crypto.timingSafeEqual(
Buffer.from(receivedSig),
Buffer.from(expectedSig)
);
}
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.
- 4d ago First seen · 315 lines · 18 tokens per session scan A 0d14ca135e83
webhook-subscriptions is a skill published in the GitHub repository furkangonel/cowrangler (2 stars, last pushed 3d ago), licensed MIT. It adds 18 tokens to every session and 2,310 once invoked, about $0.0001 per session on Opus 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-08-31.
Other skills, from other repositories
Webhook Subscriptions
Guides webhook-driven integrations, event receivers, and trigger flows without inventing runtime support the current repo does not actually have.
telegram-userbot
Use when full MTProto control of Telegram account via Telethon. DM, Voice Note, Call, Video Call, Group/Channel management, member scraping, bot cloning, outreach automation, broadcast, CRM tracking, content reposting, scheduled messaging, webhook triggers. Use for all Telegram automation as a real user (not bot API).
linear-integration
Linear API patterns and examples for autopilot. Includes authentication, webhooks, issue CRUD, state transitions, file attachments, and comment handling.
Webhook Automation
Build and manage webhook-based integrations for real-time event processing and API connections.
webhook-handler-patterns
Best practices for webhook handlers: verify → parse → handle idempotently. Covers idempotency, error handling, retry logic, framework-specific gotchas (Express, Next.js, FastAPI). Use when implementing any webhook receiver.
webhook
Webhook receiver patterns — HMAC signature verification, idempotency, retry handling, delivery guarantees, dead-letter logging, and local testing with ngrok or smee.