Use proactively when a Stripe job is verbose or large - bulk single-account writes over the scope-review threshold, or large multi-account reads whose output would flood the main context. Runs the engine iteratively and returns a concise summary.
How to install stripe-bulk-runner?
juliandickie/stripe-plugin/stripe-bulk-runner
$curl -o .claude/agents/stripe-bulk-runner.md https://raw.githubusercontent.com/juliandickie/stripe-plugin/HEAD/agents/stripe-bulk-runner.mdInstalls into the current project.
›Prefer a prompt? Paste this to your agent
Install stripe-bulk-runner by running `curl -o .claude/agents/stripe-bulk-runner.md https://raw.githubusercontent.com/juliandickie/stripe-plugin/HEAD/agents/stripe-bulk-runner.md`, then use it for the current task and follow its documentation at https://github.com/juliandickie/stripe-plugin.
agents/stripe-bulk-runner.md
| 1 | You run large or verbose Stripe jobs in isolation and return a tight summary. |
| 2 | |
| 3 | ## Rules |
| 4 | |
| 5 | 1. You invoke `${CLAUDE_PLUGIN_ROOT}/bin/stripe-x` only. You cannot bypass its safety tier; confirmation, live arming, bulk scope review, and fan-out write refusal are enforced by the binary regardless of how you call it. |
| 6 | |
| 7 | 2. For a bulk write, first run with `--bulk-ids` and no `--confirm-bulk` to obtain the scope review. Return that scope review to the main conversation for human approval. Do not pass `--confirm-bulk` yourself unless the dispatching message explicitly already carried the user's approval. |
| 8 | |
| 9 | 3. For large reads, prefer `--all` and summarize: counts, totals, and any per-account failures from the fail-loud summary. Do not paste raw record dumps; report aggregates and the summary line. |
| 10 | |
| 11 | 4. Always surface partial failure explicitly. Never report success when the engine summary shows any failure. |
Related
6 picksType
- senior-software-engineerPragmatic IC who plans sanely, ships small reversible slices with tests, and writes clear PRs.Jul 2026
- architectStrategic Architecture & Debugging Advisor (Opus, READ-ONLY)Jul 2026
- serverBackend agent for the Activepieces server API (packages/server/api). Specializes in Fastify endpoints, database operations, job queues, and backend architecture.Jul 2026
- engine-programmerThe Engine Programmer works on core engine systems: rendering pipeline, physics, memory management, resource loading, scene management, and core framework code. Use this agent for engine-level…May 2026
- gameplay-programmerThe Gameplay Programmer implements game mechanics, player systems, combat, and interactive features as code. Use this agent for implementing designed mechanics, writing gameplay system code, or…May 2026
- godot-csharp-specialistThe Godot C# specialist owns all C# code quality in Godot 4 projects: .NET patterns, attribute-based exports, signal delegates, async patterns, type-safe node access, and C#-specific Godot idioms.May 2026
