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.
git clone --depth 1 https://github.com/vibestackdev/vibe-stackWrote 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/rules/vibestackdev/vibe-stack/stripe-webhooks)<a href="https://agentmods.dev/rules/vibestackdev/vibe-stack/stripe-webhooks"><img src="https://agentmods.dev/badge/rules/vibestackdev/vibe-stack/stripe-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.
<a href="https://agentmods.dev/rules/vibestackdev/vibe-stack/stripe-webhooks"><img src="https://agentmods.dev/badge/rules/vibestackdev/vibe-stack/stripe-webhooks.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00000 | $0.00528 |
| Opus 5.5 | $0.00000 | $0.00211 |
| Sonnet 5.5 | $0.00000 | $0.00106 |
| Haiku 4.5 | $0.00000 | $0.00053 |
Grade A, and why
stripe-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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Stripe Webhook Security
RULE 1: ALWAYS Verify Webhook Signatures First
The AI will generate webhook handlers that process the payload directly. This is a CRITICAL vulnerability — anyone can POST to your webhook endpoint and trigger subscription changes, refunds, or account modifications.
import Stripe from 'stripe'
const stripe = new Stripe(process.env.STRIPE_SECRET_KEY!)
export async function POST(request: Request) {
const body = await request.text() // Must be raw text, NOT .json()
const signature = request.headers.get('stripe-signature')
if (!signature) {
return Response.json({ error: 'Missing signature' }, { status: 400 })
}
let event: Stripe.Event
try {
event = stripe.webhooks.constructEvent(
body,
signature,
process.env.STRIPE_WEBHOOK_SECRET!
)
} catch (err) {
console.error('[STRIPE_WEBHOOK_VERIFICATION_FAILED]', err)
return Response.json({ error: 'Invalid signature' }, { status: 400 })
}
// NOW it's safe to process the event
switch (event.type) {
case 'checkout.session.completed':
await handleCheckoutCompleted(event.data.object)
break
case 'customer.subscription.updated':
await handleSubscriptionUpdated(event.data.object)
break
case 'customer.subscription.deleted':
await handleSubscriptionDeleted(event.data.object)
break
}
return Response.json({ received: true })
}
RULE 2: NEVER Use request.json() for Webhooks
Stripe signature verification requires the RAW request body as a string.
If you parse it with request.json() first, the verification will ALWAYS fail
because JSON.stringify produces different whitespace than the original payload.
// ❌ WRONG — signature verification will always fail
const body = await request.json()
stripe.webhooks.constructEvent(JSON.stringify(body), sig, secret)
// ✅ CORRECT — use raw text
const body = await request.text()
stripe.webhooks.constructEvent(body, sig, secret)
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.
- 1mo ago First seen · 79 lines · 0 tokens per session scan A 1b7e7b9f4bf2
stripe-webhooks is a cursor rule published in the GitHub repository vibestackdev/vibe-stack (8 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 528 tokens. 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 cursor rules, from other repositories
payment-providers
When implementing importPayments() in provider classes.
payments
Cursor rule "payments" from shipkit-io/bones, covering payment processing best practices, payment security, webhook implementation, payment state management and error handling.
components
React component, styling, theme, accessibility, and RTL instructions.
vibe-tools
Global Rule. This rule should ALWAYS be loaded.
multi-zone-architecture
Multi-zone architecture allows Shipkit applications to be split into multiple Next.js applications while appearing as a single domain to users. This pattern is ideal for.
database-patterns
Use the createTable function with consistent naming.