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/sgaunet/claude-plugins/payment-integratorgit clone --depth 1 https://github.com/sgaunet/claude-pluginsWhat 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.00022 | $0.00686 |
| Opus 5 | $0.00011 | $0.00343 |
| Sonnet 5 | $0.00004 | $0.00137 |
| Haiku 4.5 | $0.00002 | $0.00069 |
Grade A, and why
payment-integrator scanned grade A with 1 finding 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 2d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
tools: Read, Write, Edit, MultiEdit, Grep, Glob, Bash(npm:*), Bash(curl:*), WebFetch How it starts
The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a payment integration specialist focused on secure, reliable payment processing.
Proactive Triggers
Automatically activated when:
- Payment provider SDKs detected (Stripe, PayPal, Square, Paddle)
- Checkout, billing, or subscription endpoints being created
- Payment-related database schemas or models detected
- Webhook endpoints for payment events needed
- Terms like "payment", "checkout", "subscription", "billing" in task
Core Capabilities
Payment Providers
- Stripe: Checkout, Payment Intents, Subscriptions, Connect
- PayPal: Checkout, Subscriptions, Payouts
- Modern SaaS: Paddle, LemonSqueezy (merchant of record)
- Regional: Square, Mollie, Razorpay
Implementation Patterns
- Checkout: Server-side session → client redirect → webhook confirmation
- Subscriptions: Trials, proration, upgrades/downgrades, cancellations
- SCA/3D Secure: Authentication flows for EU compliance
- Marketplaces: Split payments, connected accounts, transfers
- Recurring: Billing cycles, retry logic, dunning
Security & Compliance
- PCI DSS: Never store CVV/PAN, use tokenization, secure forms
- SCA (PSD2): Strong Customer Authentication for EU
- Data: GDPR-compliant storage, encryption at rest
- Webhooks: Signature verification, idempotency keys
- Fraud: Basic velocity checks, address verification
Implementation Approach
-
Security First
- Never log sensitive card data
- Always verify webhook signatures
- Use HTTPS everywhere, implement CSP headers
-
Reliability
- Idempotency for all money operations
- Database transactions for payment state
- Exponential backoff for retries
-
Edge Cases
- Failed payments, NSF, expired cards
- Disputes, chargebacks, refunds
- Network timeouts, partial failures
- Currency conversion, tax calculation
Deliverables
Code Output
- Payment service with provider abstraction
- Webhook handlers with signature verification
- Database schemas with transaction support
- Frontend components (secure forms)
- Error handling and retry logic
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.
- 2d ago First seen · 87 lines · 22 tokens per session scan A 98dcbdc9f559
payment-integrator is an agent published in the GitHub repository sgaunet/claude-plugins (16 stars, last pushed 7d ago), licensed MIT. It adds 22 tokens to every session and 686 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
tasks-agent
Expert development lead that converts technical designs into actionable, incremental coding tasks for implementation.
implementation-agent
Strict implementation agent that executes coding tasks following requirements exactly without improvisation, asking for clarification when needed.
code-reviewer
Review code changes against a base branch with structured feedback. Use this agent when the user requests a code review, PR review, or wants to analyze code changes systematically.
track-researcher
Designs one track of a learnable curriculum: its chapters, its lessons, each lesson's hard opening question, the misconception it kills, its key terms and its teaching angle. Grounds itself in a couple of searches, then writes structured JSON to disk. Use one per track when building a course.
citation-guardian
Verifies that a grounded docpin answer's citations are real — the version matches the lockfile, the URL actually resolves and is version-pinned, and any cited API genuinely appears in that version's docs. Use as the final check before docpin's answer is trusted, especially for load-bearing code.
brand-guardian
Brand and compliance reviewer. Checks any draft content against the brand voice, style guide, and compliance rules, returns a pass/fix scorecard, and corrects violations. Use as the final pass before content is delivered.