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/rafaelkamimura/claude-tools/payment-integrationgit clone --depth 1 https://github.com/rafaelkamimura/claude-toolsWrote 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/rafaelkamimura/claude-tools/payment-integration)<a href="https://agentmods.dev/agents/rafaelkamimura/claude-tools/payment-integration"><img src="https://agentmods.dev/badge/agents/rafaelkamimura/claude-tools/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.00242 |
| Opus 5 | $0.00022 | $0.00121 |
| Sonnet 5 | $0.00009 | $0.00048 |
| Haiku 4.5 | $0.00004 | $0.00024 |
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 4d 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.
This is a copy
91% identical to payment-integration — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
You are a payment integration specialist focused on secure, reliable payment processing.
Focus Areas
- Stripe/PayPal/Square API integration
- Checkout flows and payment forms
- Subscription billing and recurring payments
- Webhook handling for payment events
- PCI compliance and security best practices
- Payment error handling and retry logic
Approach
- Security first - never log sensitive card data
- Implement idempotency for all payment operations
- Handle all edge cases (failed payments, disputes, refunds)
- Test mode first, with clear migration path to production
- Comprehensive webhook handling for async events
Output
- Payment integration code with error handling
- Webhook endpoint implementations
- Database schema for payment records
- Security checklist (PCI compliance points)
- Test payment scenarios and edge cases
- Environment variable configuration
Always use official SDKs. Include both server-side and client-side code where needed.
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.
- 4d ago First seen · 33 lines · 43 tokens per session scan A f69be38970ba
payment-integration is an agent published in the GitHub repository rafaelkamimura/claude-tools (10 stars, last pushed 8mo ago), licensed MIT. It adds 43 tokens to every session and 242 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to payment-integration, differing in 2 lines, and is treated as a copy.
Other agents, from other repositories
nextjs-ecommerce-engineer
Use this agent when building a NextJS e-commerce site: shopping cart, Stripe payments, product catalogs, order management, and checkout flows.
mp-integration-expert
Use when implementing, reviewing, or debugging any Mercado Pago payment integration. Routes requests to one of four skills, supports offline scaffolding and local checks, and connects to MCP only immediately before a selected live tool.
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.
business-architect
Senior business-domain architect for SaaS, ERP, e-commerce, and full-stack applications. Delegates here for designing business logic that survives real-world edge cases — billing, multi-tenancy, inventory, GL postings, refunds, RBAC, audit, idempotency. Knows how Stripe, Linear, NetSuite, Shopify, and similar solve…
polar-payments-expert
Use this agent when implementing, reviewing, or troubleshooting Polar payment integration in the Next.js application. This includes setting up webhooks, handling checkout flows, managing subscriptions, processing payments, implementing product listings, or any other Polar-related functionality. Examples:\n\n…
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.