agentmods.dev

stripe-fixtures

stripe-fixtures is a skill for Claude Code from hideokamoto/stripe-testing-mcp-tools. It costs 271 tokens per session (3,546 once invoked), scanned A, original, MIT.

A guide for creating Stripe CLI fixture files: JSON descriptions of test data and linked API requests that run in sequence. Stripe is a service for online payments, and test clocks let you move simulated time forward.

In plain words
What is it for?
Use it to prepare subscription lifecycle tests, failed payments, Connect destination charges, test-clock scenarios, or many test customers. You run the finished fixture yourself with the Stripe CLI.
Why use it?
It helps avoid manually working out Stripe response paths, request formats, and long chains of related test requests. It also checks the fixture structure before you run it.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the stripe-test-mcp plugin — 4 skills, 1 MCP server shipped together

not rated 9repo 1mo ago A scan 271 tokens original MIT

Good fit Use it to prepare subscription lifecycle tests, failed payments, Connect destination charges, test-clock scenarios, or many test customers. You run the finished fixture yourself with the Stripe CLI.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/hideokamoto/stripe-testing-mcp-tools/stripe-fixtures
View source ↗ hideokamoto/stripe-testing-mcp-tools
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-fixtures
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.

agentmods badge for stripe-fixtures

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/hideokamoto/stripe-testing-mcp-tools/stripe-fixtures"><img src="https://agentmods.dev/badge/skills/hideokamoto/stripe-testing-mcp-tools/stripe-fixtures.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 271 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,546 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.00271 $0.03546
Opus 5 $0.00135 $0.01773
Sonnet 5 $0.00054 $0.00709
Haiku 4.5 $0.00027 $0.00355

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

Security

Grade A, and why

stripe-fixtures 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-fixtures/SKILL.md · 224 lines

How it starts

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

stripe-fixtures

Stripe CLI の stripe fixtures filepath で実行可能な fixture JSON を、対話を通じて整理・生成・検証する。

何を解いているか

stripe fixtures は複数の Stripe API リクエストを JSON にシーケンス化し、前のレスポンスを ${name:json_path} で参照しながら連鎖実行できる。ただし以下の理由で、人間が直接書くのは現実的ではない:

  • 参照構文を書くには Stripe API の response shape を頭に入れている必要がある
  • path / method の対応を毎回 docs で照合する必要がある
  • 同一リソースを N 個作る繰り返し構文がない（人間が N 個分の entry を手で書くのは非現実的）
  • 配列要素アクセス記法に docs と実装の食い違いがある（pitfalls.md 参照）

これは AI のスイートスポットそのもの。逆に「単発 API を MCP tool で wrap する」アプローチでは、 fixture が解いている問題（宣言的なテストデータセットアップ）には届かない。

役割の境界

担うこと:

  • 対話を通じた要件整理
  • fixture JSON の生成
  • 静的検証（参照整合性、記法、 path 形式）
  • stripe trigger で済むケースの撤退判定
  • STRIPE_API_KEY の prefix 確認指示

担わないこと:

  • fixture の実機実行（ユーザーが stripe fixtures で実行）
  • 動的検証（API レスポンス確認）
  • Live key への強制ブロック（CLI 側でないと不可能）

関連スキル（同 monorepo 内）

このリポジトリは Stripe テスト用に2つのレーンを持つ。意図に応じて使い分ける:

  • 宣言的レーン（このスキル） — stripe fixtures 用の JSON を生成。CI で再現したい・差分管理したいテストデータセット向け。実行はユーザーの Stripe CLI。
  • 命令的レーン（MCP ツール） — その場で Stripe API を叩いて test clock / 顧客 / サブスクを操作する。stripe-test-mcp MCP サーバーが提供。即座に動かして確認したいとき向け。

test clock を fixture で扱う場合の API 制約（最大3顧客/クロック、作成時のみ紐付け、前方のみ進行、Unix 秒）は、姉妹スキル stripe-test-clock-constraints に集約してある。cleanup の手順は stripe-test-data-lifecycle を参照。これらは再掲せず、必要に応じてそちらを読む。

動作フロー

このフローは順序を守る。途中で対話がスキップされると、実行できない、または意図と違う JSON が出る原因になる。

Phase 0: 撤退判定

最初にユーザーの依頼を読み、 stripe trigger で済むかを判定する。済む場合は fixture を作らずに stripe trigger の使い方を案内して終わる。

撤退する判定基準:

  • 単一の event 発火が目的で、データのカスタマイズが不要
  • 例: 「customer.subscription.created を発火したい」「invoice.payment_succeeded を一回流したい」
  • stripe trigger --help で利用可能な event 一覧が出る

撤退しない判定基準:

  • test_helpers (test_clock 系) を含む
  • 複数 customer / 複数 subscription を扱う
  • 失敗パターンの期待値を含む
  • Connect 配下のリソース操作
  • カスタム metadata や特殊な params の組み合わせ

Phase 1: 軸の確定

ユーザーの初回発話から確定していない軸だけを質問する。最大3問。それ以上聞きたくなったら「分からない部分は仮置きで JSON を生成し、コメントで明示する」に倒す。煩わしさで Skill が嫌われるリスクのほうが、軽微な仮置きより重いため。

軸 質問例 スキップ条件
時系列 時間進行を含むか、含むなら何ヶ月分か 「即時」「ワンショット」と明言済み
アカウント Connect 配下か Direct か 「Connect」or「シンプル」と明言済み
規模 単発か bulk か（件数） 件数が明示されている
結果軸 成功か、失敗を含むか 「失敗」「失敗カード」「past_due」等の語あり
通貨 JPY か USD か デフォルトは USD で進めて生成後に確認
検証目的 何を webhook で観測したいか 既に明示されている
Cleanup 使い捨てか CI 再現性必要か 明言済みなら省略

Read the full file on GitHub · 224 lines

Files

What ships with it

9 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. 11d ago First seen · 224 lines · 271 tokens per session scan A 2a28b6223087

Subscribe to this mod's changes

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

Backend and APIsTesting
Related

Other skills, from other repositories

server-side-calls

Call tRPC procedures directly from server code using t.createCallerFactory() and router.createCaller(context) for integration testing, internal server logic, and custom API endpoints. Catch TRPCError and extract HTTP status with getHTTPStatusCodeFromError(). Error handling via onError option.

trpc/trpc · 61 tokens

mem0-test-integration

Verify a Mem0 integration produced by /mem0-integrate. Runs in the same workspace on the same branch (loose coupling) — installs dependencies, runs the repo's native test suite, then exercises a real end-to-end smoke flow against the user's API key. Produces a scorecard. TRIGGER when: user has just run /mem0-integrate…

mem0ai/mem0 · 207 tokens

prowler-test-api

Testing patterns for Prowler API: JSON:API, Celery tasks, RLS isolation, RBAC. Trigger: When writing tests for api/ (JSON:API requests/assertions, cross-tenant isolation, RBAC, Celery tasks, viewsets/serializers).

prowler-cloud/prowler · 62 tokens

python-sdk

Implement or modify Python SDK behavior under python/composio, including tools, toolkits, sessions, auth configs, connected accounts, client integration, and shared Python models. Use for Python core runtime/API work; pair with python-testing and cross-sdk-parity when TypeScript must match.

ComposioHQ/composio · 60 tokens

convex-test

Generate convex-test tests for the app's Convex functions.

openclaw/clawhub · 16 tokens

voiden

Create and edit Voiden .void files for API testing. Covers the .void file format and all enabled extension block types.

VoidenHQ/voiden · 28 tokens