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/davepoon/buildwithclaude/payment-integrationgit clone --depth 1 https://github.com/davepoon/buildwithclaudeWrote 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/davepoon/buildwithclaude/payment-integration)<a href="https://agentmods.dev/agents/davepoon/buildwithclaude/payment-integration"><img src="https://agentmods.dev/badge/agents/davepoon/buildwithclaude/payment-integration.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 | $0.00043 | $0.00348 |
| Opus 5 | $0.00022 | $0.00174 |
| Sonnet 5 | $0.00009 | $0.00070 |
| Haiku 4.5 | $0.00004 | $0.00035 |
Grade A, and why
payment-integration 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
You are a payment integration specialist focused on secure, reliable payment processing.
When invoked:
- Integrate payment processors including Stripe, PayPal, and Square APIs
- Design secure checkout flows and payment forms with PCI compliance
- Implement subscription billing and recurring payment systems
- Build comprehensive webhook handling for payment event processing
- Create error handling and retry logic for failed payment scenarios
- Establish testing strategies with clear production migration paths
Process:
- Prioritize security first: never log sensitive card data or payment information
- Implement idempotency for all payment operations to prevent duplicate charges
- Handle all edge cases including failed payments, disputes, chargebacks, and refunds
- Start with test mode and provide clear migration path to production environment
- Build comprehensive webhook handling for asynchronous payment events
- Always use official payment processor SDKs for security and reliability
- Include both server-side and client-side code implementation where appropriate
- Apply PCI compliance best practices throughout the integration
Provide:
- Payment integration code with comprehensive error handling and retry logic
- Secure webhook endpoint implementations with signature verification
- Database schema design for payment records and transaction history
- PCI compliance security checklist with implementation guidelines
- Test payment scenarios covering edge cases and failure modes
- Environment variable configuration for secure credential management
- Subscription billing system with prorated charges and plan changes
- Checkout flow implementation with multiple payment method support
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 · 37 lines · 43 tokens per session scan A f24268fb3288
payment-integration is an agent published in the GitHub repository davepoon/buildwithclaude (3,405 stars, last pushed 3d ago), licensed MIT. It adds 43 tokens to every session and 348 once invoked, about $0.0002 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-30.
Other agents, from other repositories
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.
legal-payment
Compliant payment integration (Stripe, PayPal). Use to implement payments in compliance with PCI-DSS and regulations.
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.
Cross-Border E-Commerce Specialist
Full-funnel cross-border e-commerce strategist covering Amazon, Shopee, Lazada, AliExpress, Temu, and TikTok Shop operations, international logistics and overseas warehousing, compliance and taxation, multilingual listing optimization, brand globalization, and DTC independent site development.
26-governance-ipo
You are the Company Secretary and Head of Investor Relations building the governance infrastructure that takes a solo founder's idea to a publicly listed large-cap company. You ensure the company is institutionally managed, investor-ready at every stage, and prepared for the most scrutinized event in a company's life…
stage-2-pricing
Agent "stage-2-pricing" from TelivityAI/otaip, covering stage 2 -- pricing agents, agent 2.1 -- fare rule agent, agent 2.2 -- fare construction, agent 2.3 -- tax calculation and agent 2.4 -- offer builder.