What is stripe-test-data-lifecycle?

A workflow for creating, checking, and removing Stripe test data. Stripe test mode is a safe environment for simulated payments that does not use live transactions.

Use it to create test customers and subscriptions, verify billing scenarios, and clean up test data; products and prices must be created elsewhere.

It keeps test customers and subscriptions organized and removes leftover data after testing.

stripe-test-data-lifecycle — Skill for Claude Code by hideokamoto

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 hideokamoto/stripe-testing-mcp-tools --skill stripe-test-data-lifecycle

Clone the repo

git clone --depth 1 https://github.com/hideokamoto/stripe-testing-mcp-tools

Made for: Claude Code.

Or install stripe-test-mcp, the plugin that ships this one along with the rest of its 4 skills, 1 MCP server.

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/hideokamoto/stripe-testing-mcp-tools/stripe-test-data-lifecycle/github.svg)](https://agentmods.dev/skills/hideokamoto/stripe-testing-mcp-tools/stripe-test-data-lifecycle)

Your own site

<a href="https://agentmods.dev/skills/hideokamoto/stripe-testing-mcp-tools/stripe-test-data-lifecycle"><img src="https://agentmods.dev/badge/skills/hideokamoto/stripe-testing-mcp-tools/stripe-test-data-lifecycle/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/hideokamoto/stripe-testing-mcp-tools/stripe-test-data-lifecycle"><img src="https://agentmods.dev/badge/skills/hideokamoto/stripe-testing-mcp-tools/stripe-test-data-lifecycle.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 741 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.00076	$0.00741
Opus 5	$0.00038	$0.00370
Sonnet 5	$0.00015	$0.00148
Haiku 4.5	$0.00008	$0.00074

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

Security

Grade A, and why

stripe-test-data-lifecycle 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 9d 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-test-data-lifecycle/SKILL.md · 65 lines

How it starts

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

Stripe Test Data Lifecycle

A round-trip workflow for Stripe test data: set up, verify, then clean up so the test account stays tidy. Test mode only (live keys are rejected).

1. Setup

Customers: create_stripe_test_customers
- number (default 1), and optional name, email, description, payment_method_id, test_clock.
- Every customer created here is tagged with metadata.generator = stripe-testing-tools-mcp. The MCP server has no tool to list or search customers by metadata, so record the ids returned at creation for later cleanup. The tag is still useful for finding leftovers in the Stripe Dashboard or Stripe CLI.
- If attaching a test_clock, keep number at most 3 (see stripe-test-clock-constraints).
Subscriptions: create_stripe_test_subscription
- customer, items ([{ price, quantity }]), optional proration_behavior, payment_method_id.
Products/prices: create these with your normal Stripe tooling or Dashboard; this MCP only archives/deletes products, it does not create them.

2. Verify

Run your scenario (for time-based billing, follow stripe-billing-cycle-test).
Confirm results (invoices, subscription status, charges) via the Stripe Dashboard in test mode or the Stripe API. The MCP does not expose list/read tools for these objects.

3. Cleanup (recommended order)

Tear down dependents before their dependencies to avoid leftover references:

Delete customers: delete_stripe_test_customers
- customer_ids: array of ids to delete. You must use the ids collected at creation — the MCP cannot search customers by generator metadata. To recover lost ids, look them up in the Stripe Dashboard or CLI.
- Deleting a customer immediately cancels its associated subscriptions (Stripe: Delete a customer), so do this before touching products.
Archive products: archive_stripe_test_products
- product_ids and/or urls. Archiving sets active: false and is non-destructive (recoverable). Prefer this when a product may still be referenced or you want a soft cleanup.
Delete products (optional, permanent): delete_stripe_test_products
- product_ids and/or urls. Permanent and irreversible. Stripe only lets you delete a product with no active prices/usage; if deletion fails, archive instead. Confirm the exact deletability rules against the Stripe docs when in doubt.

Read the full file on GitHub · 65 lines

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.

9d ago First seen · 65 lines · 76 tokens per session scan A 327832fc24e0

Subscribe to this mod's changes

stripe-test-data-lifecycle is a skill published in the GitHub repository hideokamoto/stripe-testing-mcp-tools (9 stars, last pushed 1mo ago), licensed MIT. It adds 76 tokens to every session and 741 once invoked, about $0.0004 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.

E-commerce Testing

qa

QA-test a website or web app and return a 1-5 quality score (5 = flawless, 1 = broken) with evidence. Use when the user wants to test, QA, evaluate, score, or "check how good" a site, page, flow, or app — including a local dev server (e.g. "qa test localhost:5173", "does the checkout work?", "rate this landing page").…

browser-use/browser-use · 103 tokens

stripe-test-data-lifecycle

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Stripe Test Data Lifecycle

1. Setup

2. Verify

3. Cleanup (recommended order)

What this file has done since we first saw it

Other skills, from other repositories

qa

synthetic-monitoring

visual-regression-testing

shopify-ab-testing

postgres-commit-history-article

setup-trtmc-environment