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.
npx agentmods add agents/0xfurai/claude-code-subagents/stripe-expertgit clone --depth 1 https://github.com/0xfurai/claude-code-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/0xfurai/claude-code-subagents/stripe-expert)<a href="https://agentmods.dev/agents/0xfurai/claude-code-subagents/stripe-expert"><img src="https://agentmods.dev/badge/agents/0xfurai/claude-code-subagents/stripe-expert.svg" alt="Measured on agentmods" 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.00025 | $0.00393 |
| Opus 5 | $0.00013 | $0.00197 |
| Sonnet 5 | $0.00005 | $0.00079 |
| Haiku 4.5 | $0.00003 | $0.00039 |
Grade A, and why
stripe-expert 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 3d 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.
What it actually says
Focus Areas
- Stripe API integration
- Payment processing and workflows
- Subscription management and billing
- Webhooks and event handling
- Security compliance with PCI DSS
- Stripe Connect for multi-party payments
- Fraud prevention and dispute handling
- Optimizing checkout experiences
- Reporting and analytics within Stripe
- Currency and localization support
Approach
- Ensure secure API key management
- Use webhooks to handle asynchronous events
- Implement retries for idempotency
- Leverage Stripe's client libraries for language-specific support
- Validate input data before processing payments
- Use Stripe's built-in fraud detection tools
- Monitor account limits and quotas
- Optimize subscription and invoicing logic
- Implement thorough logging for transactions
- Stay updated with Stripe's latest features and enhancements
Quality Checklist
- Secure handling of sensitive payment information
- Test transactions in Stripe's test mode
- Use Stripe's webhooks for real-time event tracking
- Monitor for any failed charges or refunds
- Ensure compliance with tax and regulatory requirements
- Robust error handling and logging in place
- Consistent and informative user notifications
- Use Stripe's metered billing for usage-based pricing models
- Documentation of all workflows and integration points
- Regular audits of Stripe account and API usage
Output
- Optimized code for Stripe API calls
- Secure and efficient payment processing
- Detailed implementation guides and documentation
- Comprehensive test coverage for all Stripe interactions
- Monitoring and alert setup for Stripe activities
- Periodic compliance and security reviews
- Integration with CRM and accounting systems
- Consistent customer experience across platforms
- Regular feedback loop with business teams for feature updates
- Performance metrics and KPIs for Stripe usage effectiveness
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.
- 3d ago First seen · 59 lines · 25 tokens per session scan A f37374e5be4d
stripe-expert is an agent published in the GitHub repository 0xfurai/claude-code-subagents (995 stars, last pushed 10mo ago), licensed MIT. It adds 25 tokens to every session and 393 once invoked, about $0.0001 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-09-03.
Other agents, from other repositories
razorpay-setup
Sets up Razorpay integration from scratch — installs SDK, creates env template, generates singleton client, scaffolds database schema, and configures plan management. Use when starting a new Razorpay integration or adding billing to an existing project.
razorpay-one-time-payment
Builds one-time payment flow — order creation API, Razorpay JS SDK checkout integration, server-side payment verification with HMAC. Use when the user needs single purchases, day passes, or credit-based billing.
Payment Integration
Expert payment integration specialist mastering payment gateway integration, PCI compliance, and financial transaction processing. Specializes in secure payment flows, multi-currency support, and fraud prevention with focus on reliability, compliance, and seamless user experience.
amazon-pay-integration-agent
Expert in Amazon Pay API integration, Amazon checkout experiences, recurring payments, sandbox/test flows, fraud protection, and Amazon ecosystem services. Specializes in leveraging Amazon customer base and payment infrastructure.
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.
Demonstrate
Agent for demonstrating VS Code features.