agentmods.dev

stack-stripe

stack-stripe is a skill for Claude Code from e-t-y-b/etyb-skills. It costs 223 tokens per session (4,171 once invoked), scanned A, original, MIT.

A reference pack that gives an engineering team current guidance about Stripe's payment and financial products and directs different roles to the relevant information.

In plain words
What is it for?
Use it when building with Stripe Payments, Billing, Connect, Tax, Radar, Issuing or other listed Stripe services.
Why use it?
Stripe covers many products, so the pack helps a team find the right product and role-specific guidance while keeping existing specialists responsible for the work.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: mentions Claude Code; mentions Codex.

Part of the etyb plugin — 14 skills, 5 agents, 4 hooks shipped together

not rated 10repo 2mo ago A scan 223 tokens original MIT

Good fit Use it when building with Stripe Payments, Billing, Connect, Tax, Radar, Issuing or other listed Stripe services.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/e-t-y-b/etyb-skills/stripe
View source ↗ e-t-y-b/etyb-skills etyb.ai
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 e-t-y-b/etyb-skills --skill stripe
Clone the repo
git clone --depth 1 https://github.com/e-t-y-b/etyb-skills

Made for: Claude Code.

Or install etyb, the plugin that ships this one along with the rest of its 14 skills, 5 agents, 4 hooks.

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 stack-stripe

README.md
[![agentmods](https://agentmods.dev/badge/skills/e-t-y-b/etyb-skills/stripe/github.svg)](https://agentmods.dev/skills/e-t-y-b/etyb-skills/stripe)
Your own site
<a href="https://agentmods.dev/skills/e-t-y-b/etyb-skills/stripe"><img src="https://agentmods.dev/badge/skills/e-t-y-b/etyb-skills/stripe/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 stack-stripe

Your own site · 80×15
<a href="https://agentmods.dev/skills/e-t-y-b/etyb-skills/stripe"><img src="https://agentmods.dev/badge/skills/e-t-y-b/etyb-skills/stripe.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 223 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,171 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.00223 $0.04171
Opus 5 $0.00112 $0.02086
Sonnet 5 $0.00045 $0.00834
Haiku 4.5 $0.00022 $0.00417

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

Security

Grade A, and why

stack-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 12d 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.

stacks/stripe/SKILL.md · 142 lines

How it starts

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

Stripe Stack — Team Briefing

This is a knowledge overlay, not a new specialist. The existing ETYB team does the work — backend-architect writes the backend code, devops-engineer wires the deploys, security-engineer enforces the boundary. This pack tells each role where the current Stripe knowledge lives.

Where the full briefing lives

The full Stack briefing lives in this same folder. Per-product and per-role pages are siblings of this SKILL.md. Every page carries last_verified_on stamps and authoritative-source URLs in its frontmatter; see skills/etyb/core/knowledge-currency.md for the drift-check protocol that uses them.

  • Stack briefing: stacks/stripe/index.md
  • Per-product pages: stacks/stripe/<product>.md — one per entry in products_covered above
  • Per-role views: stacks/stripe/<role>.md — one per role in applies_to_roles above

When ETYB is installed locally these are read directly from disk. For third-party agents without the install, the same content is reachable as raw markdown at https://raw.githubusercontent.com/e-t-y-b/etyb-skills/main/stacks/stripe/<page>.md.

When delegate_to_skills (frontmatter above) lists a first-party vendor MCP/skill that's installed in the user's environment, ETYB defers to it first. The in-repo Stack content is the curated fallback.

What changed in 2025-2026 that older training data misses

Critical context — an LLM with a 2024 cutoff will get these wrong:

  • Meter API replaced usage_records for net-new usage-based billing. The old subscription_item.create_usage_record pattern is deprecated for new subscriptions (announced late 2024). New work uses /v1/billing/meter_events and a billing.meter object that prices via the new billing.meter_event_summary aggregation. Existing legacy usage-record subscriptions still work; new ones must use Meters.
  • Connect "Custom" type is now controller properties. Account creation in 2024+ uses controller configuration (controller.fees.payer, controller.losses.payments, controller.stripe_dashboard.type, controller.requirement_collection) rather than the older type: 'custom' | 'express' | 'standard' shorthand. The legacy shorthands still work but are mapped internally to controller properties.
  • Stripe Workbench (2024) is the developer surface inside Dashboard. The old "Developers" tab is being phased into Workbench — API logs, events, webhook endpoints, version pin all live there.
  • API version pinning — every Stripe account is auto-pinned to a version on first call. A new account today gets 2025-11-15.acacia (or whatever is current). An account created in 2019 is still pinned to a 2019 version unless someone upgrades it. The same code against two accounts can return different JSON.
  • Express Checkout Element (GA 2024) consolidates Apple Pay, Google Pay, Link, Amazon Pay, PayPal into a single button row. Replaces hand-wired Payment Request Button + individual wallet integrations.
  • Payment Element (the unified Element) is the modern default; the legacy Card Element should not be used for new builds.
  • SCA / 3D Secure 2 is mandatory in EU/UK/EEA. PaymentIntents handle this automatically when automatic_payment_methods.enabled: true and you use the confirmation flow correctly. The legacy Sources API and direct Charges flow do NOT handle SCA cleanly.
  • Idempotency Key TTL is contractually guaranteed at 24 hours since 2024. Earlier guidance treated it as "best effort" — now it's a real guarantee, but only for 24 hours. Long-running retry chains beyond 24h must mint new keys.
  • Restricted API keys with scoped permissions are GA and recommended for any service-to-Stripe integration that doesn't need full secret-key power. The "one secret key for everything" pattern is a security smell in 2026.
  • Stripe-hosted MCP server (docs.stripe.com/mcp) shipped in 2025 for select operations. AI agents (Claude, Cursor, Codex) can drive Stripe via MCP tools. Production usage requires a scoped restricted key and full audit logging.
  • Stripe Connect onboarding via account_link with type: account_onboarding is the modern pattern. Legacy email-based "Connect Onboarding" redirects are being phased out.
  • Treasury matured in 2025-2026 with RTP and FedNow rails for OutboundPayments; eligibility is partner-bank-dependent and gated to approved platforms.

Read the full file on GitHub · 142 lines

Files

What ships with it

42 files 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.

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. 12d ago First seen · 142 lines · 223 tokens per session scan A 91209e9aa04b

Subscribe to this mod's changes

stack-stripe is a skill published in the GitHub repository e-t-y-b/etyb-skills (10 stars, last pushed 2mo ago), licensed MIT. It adds 223 tokens to every session and 4,171 once invoked, about $0.0011 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-08-31.

Claude CodeE-commerceFinance and fintechagentskillsai-agentarchitecture
Related

Other skills, from other repositories

stripe

Read Stripe account state from a terminal or agent: balance, payment intents, and subscriptions — and perform guarded mutations like canceling a subscription — backed by a bundled stripe-cli script that is read-only first and gates every state-changing command behind a --dry-run/--yes confirmation. Use when an agent…

magnus919/agent-skills · 116 tokens

payments

This skill should be used when adding payments, subscriptions, billing, or pricing to a SaaS — Stripe integration, checkout, plans, the customer portal, webhooks, or deciding a pricing model. Trigger phrases include "add Stripe", "accept payments", "add a subscription", "charge users", "pricing tiers", "checkout"…

MartinOlivero/saas-builder · 110 tokens

asc-ppp-pricing

Set territory-specific pricing for subscriptions and in-app purchases using current asc setup, pricing summary, price import, and price schedule commands. Use when adjusting prices by country or implementing localized PPP strategies.

rorkai/app-store-connect-cli-skills · 45 tokens

stripe

Stripe API integration with managed OAuth. Manage customers, subscriptions, invoices, products, prices, and payments. Use this skill when users want to process payments, manage billing, or handle subscriptions with Stripe. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway).…

CraftOS-dev/CraftBot · 79 tokens

meter-chargeback

CocoMeter chargeback and FinOps governance. Usage: $meter chargeback refresh | $meter chargeback invoice | $meter chargeback onboarding.

Snowflake-Labs/cocoplus · 33 tokens

Freelance Empire

Complete freelance business operating system — from first client to six-figure solo business. Covers positioning, pricing, proposals, client management, finances, scaling, and the transition from side-hustle to full-time. Use when starting freelancing, raising rates, managing clients, building recurring revenue, or…

LeoYeAI/openclaw-master-skills · 71 tokens