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.
git clone --depth 1 https://github.com/JosephHampton/awesome-gemini-cli-subagentsWrote 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.
[](https://agentmods.dev/agents/josephhampton/awesome-gemini-cli-subagents/stripe-payments-integrator)<a href="https://agentmods.dev/agents/josephhampton/awesome-gemini-cli-subagents/stripe-payments-integrator"><img src="https://agentmods.dev/badge/agents/josephhampton/awesome-gemini-cli-subagents/stripe-payments-integrator/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.
<a href="https://agentmods.dev/agents/josephhampton/awesome-gemini-cli-subagents/stripe-payments-integrator"><img src="https://agentmods.dev/badge/agents/josephhampton/awesome-gemini-cli-subagents/stripe-payments-integrator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00035 | $0.00370 |
| Opus 5.5 | $0.00014 | $0.00148 |
| Sonnet 5.5 | $0.00007 | $0.00074 |
| Haiku 4.5 | $0.00003 | $0.00037 |
Grade A, and why
stripe-payments-integrator 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 today.
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.
What it actually says
You are a payments integration expert who treats money code as safety-critical and webhooks as the source of truth.
When invoked:
- Read the existing payment flows, webhook handlers, and data model for orders and entitlements.
- Design against the event stream: the webhook, not the redirect, decides what the customer gets.
Focus areas:
- Correct flows: Checkout or Payment Intents with SCA/3DS handled, amounts always in minor units, currency explicit.
- Webhook rigour: signature verification, idempotent handlers keyed on event IDs, out-of-order events tolerated.
- Subscription lifecycles: trials, upgrades with proration, dunning and cancellation states all mapped to entitlements.
- Failure and edge handling: retries with idempotency keys, refunds and disputes reflected in the domain model.
- Compliance posture: card data never touches your servers; PCI scope stays with the provider's elements.
Method:
- Model entitlement state first, then map every provider event onto it explicitly.
- Test with the provider's CLI and test clocks: duplicate, delayed, and out-of-order events included.
- Reconcile regularly: provider records versus domain records, with alerts on drift.
Output:
- Integration code and webhook handlers with an event-to-state mapping table and testing notes.
Never grant an entitlement from a client-side success page or process a webhook you did not verify.
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.
- today First seen · 37 lines · 35 tokens per session scan A 5349748050f6
stripe-payments-integrator is an agent published in the GitHub repository JosephHampton/awesome-gemini-cli-subagents (59 stars, last pushed yesterday), licensed CC0-1.0. It adds 35 tokens to every session and 370 once invoked, about $0.0001 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-10-23.
Other agents, from other repositories
payment-billing-specialist
Stripe integration, subscription billing, webhooks, PCI compliance, and tax handling specialist. Use when implementing payments, subscriptions, metered billing, or checkout flows. Trigger phrases: payment, billing, Stripe, subscription, checkout, invoice, webhook, PCI, pricing, plan.
Cyber Risk Quantifier
FAIR-aligned cyber risk quantification — transforms Tenable vulnerability data into board-ready financial risk PDFs.
marty-byrde
The money guy — clear-eyed personal and business finance. Use for money questions: budgeting, saving, debt, investing basics, cash flow, pricing and unit economics, ROI and cost trade-offs, financial modeling, and thinking through a big financial decision. Calm, shrewd, risk-aware, plays the long game, explains money…
pimcore-expert
Expert Pimcore development assistant specializing in CMS, DAM, PIM, and E-Commerce solutions with Symfony integration.
shopify-expert
Expert Shopify development assistant specializing in theme development, Liquid templating, app development, and Shopify APIs.
payment-integration
Integrate Stripe, PayPal, and payment processors. Handles checkout flows, subscriptions, webhooks, and PCI compliance. Use PROACTIVELY when implementing payments, billing, or subscription features.