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/PayRequest/claude-pluginsWrote 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/payrequest/claude-plugins/payment-integration)<a href="https://agentmods.dev/agents/payrequest/claude-plugins/payment-integration"><img src="https://agentmods.dev/badge/agents/payrequest/claude-plugins/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/payrequest/claude-plugins/payment-integration"><img src="https://agentmods.dev/badge/agents/payrequest/claude-plugins/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.00043 | $0.00243 |
| Opus 5.5 | $0.00017 | $0.00097 |
| Sonnet 5.5 | $0.00009 | $0.00049 |
| 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 1mo 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
100% identical to payment-integration — 0 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.
- 1mo ago First seen · 33 lines · 43 tokens per session scan A 7c2c32d85d00
payment-integration is an agent published in the GitHub repository PayRequest/claude-plugins (11 stars, last pushed 1y ago), licensed MIT. It adds 43 tokens to every session and 243 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to payment-integration, differing in 0 lines, and is treated as a copy.
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.
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.