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 rules/nedcodes-ok/cursorrules-collection/stripegit clone --depth 1 https://github.com/nedcodes-ok/cursorrules-collectionWrote 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/nedcodes-ok/cursorrules-collection/stripe)<a href="https://agentmods.dev/rules/nedcodes-ok/cursorrules-collection/stripe"><img src="https://agentmods.dev/badge/rules/nedcodes-ok/cursorrules-collection/stripe.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.00331 | $0.00331 |
| Opus 5 | $0.00166 | $0.00166 |
| Sonnet 5 | $0.00066 | $0.00066 |
| Haiku 4.5 | $0.00033 | $0.00033 |
Grade A, and why
stripe 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 today.
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.
What it actually says
Stripe Integration Rules
API Usage
- Use the official Stripe SDK, not raw HTTP calls
- Always use API versioning — pin to a specific version in your Stripe config
- Store Stripe secret keys in environment variables only, never in source code
- Use test mode keys (sk_test_) during development, never live keys
Webhooks
- Always verify webhook signatures using stripe.webhooks.constructEvent()
- Handle events idempotently — the same event may be delivered multiple times
- Return 200 immediately, process asynchronously for long-running operations
- Log raw webhook payloads for debugging, but redact sensitive fields
Checkout & Payments
- Use Stripe Checkout or Payment Elements — do not build custom card forms
- Always create PaymentIntents server-side, never client-side
- Store customer IDs in your database, not full payment details
- Handle payment failures gracefully — show specific error messages from Stripe
Subscriptions
- Use Stripe's subscription lifecycle webhooks (customer.subscription.updated, etc.)
- Never trust client-side subscription status — always verify server-side
- Handle proration when changing plans
- Implement dunning (failed payment retry) handling via webhooks
Anti-patterns
- Do not store card numbers, CVVs, or full card details anywhere in your system
- Do not rely on client-side price calculations — always confirm amounts server-side
- Do not skip webhook signature verification, even in development
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.
- today First seen · 36 lines · 331 tokens per session scan A d9c2fb12a3b4
stripe is a cursor rule published in the GitHub repository nedcodes-ok/cursorrules-collection (37 stars, last pushed 6mo ago), licensed MIT. It adds 331 tokens to every session, about $0.0017 per session on Opus 5. 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-09-03.
Other cursor rules, from other repositories
10-feature-development
Feature implementation workflow and engineering mindset.
11-template-conventions
Reusable building blocks shipped with this template - use them instead of writing new ones.
03-ui
UI, layout, theming and localization standards.
12-new-project
Workflow for starting a new app from this template - rebranding, identity, cleanup and first feature.
13-updating-project
Workflow for updating an existing project - dependency and SDK upgrades, migrations, refactors, bug fixes.
01-tech-stack
Android tech stack and project standards.