stripe-billing-context

stripe-billing-context is a skill for Claude Code, Codex from appeeky/stripe-skills. It costs 0 tokens per session (387 once invoked), scanned A, original, MIT.

A shared written record of a Stripe account’s business model, products, prices, payment events, email flows, and revenue targets. Stripe is a service for taking payments and managing subscriptions.

In plain words
What is it for?
Use it to document plans, price levels, trials, add-ons, webhooks, customer billing settings, and targets for recurring revenue, churn, overdue subscriptions, and payment recovery.
Why use it?
It gives related billing work one reliable set of facts, reducing repeated questions and incorrect assumptions. It can be updated when pricing or payment-system design changes.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to document plans, price levels, trials, add-ons, webhooks, customer billing settings, and targets for recurring revenue, churn, overdue subscriptions, and payment recovery.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/appeeky/stripe-skills/stripe-billing-context
Install

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.

Any agent
npx skills add appeeky/stripe-skills --skill stripe-billing-context
Clone the repo
git clone --depth 1 https://github.com/appeeky/stripe-skills

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for stripe-billing-context

README.md
[![agentmods](https://agentmods.dev/badge/skills/appeeky/stripe-skills/stripe-billing-context/github.svg)](https://agentmods.dev/skills/appeeky/stripe-skills/stripe-billing-context)
Your own site
<a href="https://agentmods.dev/skills/appeeky/stripe-skills/stripe-billing-context"><img src="https://agentmods.dev/badge/skills/appeeky/stripe-skills/stripe-billing-context/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.

agentmods 80×15 button for stripe-billing-context

Your own site · 80×15
<a href="https://agentmods.dev/skills/appeeky/stripe-skills/stripe-billing-context"><img src="https://agentmods.dev/badge/skills/appeeky/stripe-skills/stripe-billing-context.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 387 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00387
Opus 5 $0.00000 $0.00193
Sonnet 5 $0.00000 $0.00077
Haiku 4.5 $0.00000 $0.00039

Measured 11d ago against content hash f06f862800c3, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

stripe-billing-context 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 11d 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.

skills/stripe-billing-context/SKILL.md · 63 lines

What it actually says

Stripe Billing Context

Produce stripe-billing-context.md in the workspace so every Stripe skill shares the same facts.

Gather (ask or infer)

  1. Business name + Stripe account (get_stripe_account_info)
  2. Products & prices (GetPrices, GetProducts — active only)
  3. Subscription model (monthly/annual, trials, add-ons)
  4. Webhook endpoints (from codebase + Dashboard)
  5. Customer Portal enabled? Billing emails configured?
  6. KPI targets: MRR goal, acceptable churn, past-due threshold

MCP Calls

get_stripe_account_info → {}
stripe_api_read GetProducts { parameters: { active: true, limit: 100 } }
stripe_api_read GetPrices { parameters: { active: true, limit: 100, type: recurring } }

Output Template

# Stripe Billing Context

## Account
- Display name:
- Account ID:
- Mode: live / test

## Revenue Model
- Primary product:
- Price tiers:
- Trials:
- Add-ons:

## Integrations
- Webhook URL:
- Events subscribed:
- Customer Portal:
- Payment failed emails:

## KPI Targets
| Metric | Target |
|--------|--------|
| MRR | |
| Monthly churn | < % |
| Past due subs | < N |
| Dunning recovery | > % |

## Notes

Re-run when pricing or webhook architecture changes.

Changes

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.

  1. 11d ago First seen · 63 lines · 0 tokens per session scan A f06f862800c3

Subscribe to this mod's changes

stripe-billing-context is a skill published in the GitHub repository appeeky/stripe-skills (5 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 387 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.

Related

Other skills, from other repositories

marketplace-purchase-vetting

Use this when the user asks whether a local listing is a scam, "too good to be true," worth looking at, or a good deal. Also use this when he asks you to find options — search/discover candidates, then vet the best ones. The goal is not a generic buying guide; it is a practical risk read with clear next steps.

AtlasOmnia/donna-starter · 72 tokens

saas-billing

Implement and audit SaaS billing systems, subscription state machines, secure webhooks, and local database synchronization / Implementasi dan audit sistem billing SaaS, state machine langganan, webhook aman, dan sinkronisasi database lokal.

roedyrustam/vibes-plug · 51 tokens

payment-gateway-expert

Expert guide for integrating payment gateways (Stripe, PayPal, Xendit, Midtrans, DOKU) and secure webhooks into SaaS platforms / Panduan ahli integrasi payment gateway dan webhook aman.

roedyrustam/vibes-plug · 49 tokens

szamlazzhu-document-xml-compatibility

Integrate another WooCommerce plugin with Integration for Szamlazz.hu & WooCommerce document generation. Covers WCSzamlazz()->generateinvoice(), wcszamlazzxml, wcszamlazzinvoicelineitem, wcszamlazzbeforegenerateinvoicecheck, document meta, Action Scheduler deferral, Pro webhooks/IPN including HPOS-safe custom…

Lonsdale201/wp-agent-skills · 167 tokens

szamlazzhu-vat-checkout-compatibility

Make WooCommerce checkout, B2B, VAT/tax-number, address, and headless checkout code compatible with Integration for Szamlazz.hu & WooCommerce. Covers the classic checkout field wcszamlazzadoszam, order meta billingwcszamlazzadoszam and wcszamlazzadoszamdata, user meta wcszamlazzadoszam, Checkout Block/Store API…

Lonsdale201/wp-agent-skills · 169 tokens

wc-stripe-future-payments

Design or audit WooCommerce Stripe payment flows that save a reusable method and charge it later. Covers SetupIntent versus PaymentIntent, charge-now-and-save, deposits and installment series, setupfutureusage=offsession, Stripe Customer ownership, explicit consent/mandates, later off-session PaymentIntents, SCA…

Lonsdale201/wp-agent-skills · 149 tokens