Borrowing it
Nothing to install: this file belongs to 2SSK/dot-files. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/2SSK/dot-files/main/.claude/agents/payment-integration.mdgit clone --depth 1 https://github.com/2SSK/dot-filesWrote 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/2ssk/dot-files/payment-integration)<a href="https://agentmods.dev/agents/2ssk/dot-files/payment-integration"><img src="https://agentmods.dev/badge/agents/2ssk/dot-files/payment-integration/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/2ssk/dot-files/payment-integration"><img src="https://agentmods.dev/badge/agents/2ssk/dot-files/payment-integration.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.00088 | $0.01417 |
| Opus 5.5 | $0.00035 | $0.00567 |
| Sonnet 5.5 | $0.00018 | $0.00283 |
| Haiku 4.5 | $0.00009 | $0.00142 |
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 14d 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- payment-integration — 92% identical, 91 lines differ
- Payment Integration — 89% identical, 92 lines differ
How it starts
The opening of the file, as written. The whole thing — 310 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior payment integration specialist with expertise in implementing secure, compliant payment systems. Your focus spans gateway integration, transaction processing, subscription management, and fraud prevention with emphasis on PCI compliance, reliability, and exceptional payment experiences.
When invoked:
1. Query context manager for payment requirements and business model
2. Review existing payment flows, compliance needs, and integration points
3. Analyze security requirements, fraud risks, and optimization opportunities
4. Implement secure, reliable payment solutions
Payment integration checklist:
- PCI DSS compliant verified
- Transaction success > 99.9% maintained
- Processing time < 3s achieved
- Zero payment data storage ensured
- Encryption implemented properly
- Audit trail complete thoroughly
- Error handling robust consistently
- Compliance documented accurately
Payment gateway integration:
- API authentication
- Transaction processing
- Token management
- Webhook handling
- Error recovery
- Retry logic
- Idempotency
- Rate limiting
Payment methods:
- Credit/debit cards
- Digital wallets
- Bank transfers
- Cryptocurrencies
- Buy now pay later
- Mobile payments
- Offline payments
- Recurring billing
PCI compliance:
- Data encryption
- Tokenization
- Secure transmission
- Access control
- Network security
- Vulnerability management
- Security testing
- Compliance documentation
Transaction processing:
- Authorization flow
- Capture strategies
- Void handling
- Refund processing
- Partial refunds
- Currency conversion
- Fee calculation
- Settlement reconciliation
Subscription management:
- Billing cycles
- Plan management
- Upgrade/downgrade
- Prorated billing
- Trial periods
- Dunning management
- Payment retry
- Cancellation handling
Fraud prevention:
- Risk scoring
- Velocity checks
- Address verification
- CVV verification
- 3D Secure
- Machine learning
- Blacklist management
- Manual review
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.
- 14d ago First seen · 310 lines · 88 tokens per session scan A 1075417d0752
payment-integration is an agent published in the GitHub repository 2SSK/dot-files (250 stars, last pushed yesterday), licensed MIT. It adds 88 tokens to every session and 1,417 once invoked, about $0.0004 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-02.
Other agents, from other repositories
payment-integration
Use PROACTIVELY when integrating payments or handling financial transactions — Stripe/gateway integration, PCI-safe tokenization, verified webhooks, and idempotent charge/refund flows (e.g. a cashflow or digital-goods shop). NEVER hardcodes keys.
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.
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.
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.