What is stripe-customer-portal-defaults?

A set of implementation guidelines for using Stripe Customer Portal as the self-service billing area. Stripe is a payment platform, and the portal lets customers manage an existing subscription themselves.

It helps configure the portal, create portal sessions and deep links, restrict available plan changes, and synchronize subscription changes received through webhooks.

It defines how plan changes, payment updates, cancellations, invoices, return links, and billing-state updates should fit together.

stripe-customer-portal-defaults — Skill by andrewsrigom/agent-skills

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 andrewsrigom/agent-skills --skill stripe-customer-portal-defaults

Clone the repo

git clone --depth 1 https://github.com/andrewsrigom/agent-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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/andrewsrigom/agent-skills/stripe-customer-portal-defaults/github.svg)](https://agentmods.dev/skills/andrewsrigom/agent-skills/stripe-customer-portal-defaults)

Your own site

<a href="https://agentmods.dev/skills/andrewsrigom/agent-skills/stripe-customer-portal-defaults"><img src="https://agentmods.dev/badge/skills/andrewsrigom/agent-skills/stripe-customer-portal-defaults/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/andrewsrigom/agent-skills/stripe-customer-portal-defaults"><img src="https://agentmods.dev/badge/skills/andrewsrigom/agent-skills/stripe-customer-portal-defaults.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 57 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 784 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.

Model	Per session	Once invoked
Fable 5.1	$0.00057	$0.00784
Opus 5.5	$0.00023	$0.00314
Sonnet 5.5	$0.00011	$0.00157
Haiku 4.5	$0.00006	$0.00078

Measured 2mo ago against content hash 6d26e2f54ab4, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

stripe-customer-portal-defaults 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 2mo 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.

stripe/stripe-customer-portal-defaults/SKILL.md · 89 lines

How it starts

The opening of the file, as written. The whole thing — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Stripe Customer Portal Defaults

Use this skill when the task is about self-serve billing management after the initial purchase.

Scope

when to default to the customer portal
portal configuration in sandbox and live mode
product-catalog boundaries for plan changes
portal session creation and return URLs
webhook expectations after portal-driven changes

Routing cues

billing portal, customer portal, manage billing, change plan, update payment method, cancel at period end, invoice history, portal session, deep links, or self-serve billing UX -> use this skill
initial checkout and pricing model work -> use stripe-checkout-and-pricing-model-defaults
webhook mechanics, signature verification, and idempotent event handling -> use stripe-webhook-first-billing-state
lifecycle semantics for what a subscription change means -> use stripe-subscriptions-lifecycle-and-entitlements

Default path

Use the customer portal as the default self-serve billing surface.
Configure portal features first in the Stripe Dashboard for sandbox and live mode separately.
If customers can switch plans, make sure the product catalog and allowed prices are configured intentionally.
Create portal sessions server-side for authenticated customers only.
Provide a stable return_url back into the account or billing area.
Listen to subscription, payment-method, customer, and invoice-related webhook events to sync internal state after portal actions.

When to deviate

Build a custom billing-management UI only when the product needs workflows the portal cannot support.
Use multiple portal configurations only when customer segments or platform requirements genuinely differ.
Use portal deep links when a specific self-serve action should be the landing point from your app.

Guardrails

Authenticate the user in your app before creating a portal session.
Treat the portal as a billing-management surface, not as an identity surface.
Keep portal configuration separate between sandbox and live mode.
Let Stripe own plan-change billing mechanics where possible.
Sync app state from webhooks after portal actions.

Read the full file on GitHub · 89 lines

Files

What ships with it

1 file 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.

references/self-serve-portal-defaults.md 831 B

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.

2mo ago First seen · 89 lines · 57 tokens per session scan A 6d26e2f54ab4

Subscribe to this mod's changes

stripe-customer-portal-defaults is a skill published in the GitHub repository andrewsrigom/agent-skills (2 stars, last pushed 7mo ago), licensed MIT. It adds 57 tokens to every session and 784 once invoked, about $0.0002 per session on Opus 5.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-08-31.

E-commerce Finance and fintech

stripe-customer-portal-defaults next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
stripe-customer-portal-defaultsandrewsrigom/agent-skills	Skill	2	7mo ago	MIT	A	57	Claude Code, Codex
asc-ppp-pricingrorkai/app-store-connect-cli-skills	Skill	1.1k	today	MIT	A	45	Claude Code
snaplii-cliSnaplii-Inc/agent-to-merchant-payments	Skill	812	3d ago	Apache-2.0	A	184	Claude Code
stripeCraftOS-dev/CraftBot	Skill	405	3d ago	MIT	A	79	Claude Code, Codex
ai-slopwaybarrios/opencode-power-pack	Skill	551	5d ago	MIT	A	61	Claude Code
stripemagnus919/agent-skills	Skill	170	yesterday	MIT	A	116	Claude Code, Codex
asc-ppp-pricinghanamizuki/solopreneur	Skill	156	4d ago	MIT	A	45	Claude Code