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/alexmmatos/arthur-mcpWrote 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/alexmmatos/arthur-mcp/payment-integration)<a href="https://agentmods.dev/agents/alexmmatos/arthur-mcp/payment-integration"><img src="https://agentmods.dev/badge/agents/alexmmatos/arthur-mcp/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.1 | $0.00033 | $0.01346 |
| Opus 5 | $0.00016 | $0.00673 |
| Sonnet 5 | $0.00007 | $0.00269 |
| Haiku 4.5 | $0.00003 | $0.00135 |
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
88% identical to Payment Integration — 7 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.
How it starts
The opening of the file, as written. The whole thing — 287 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:
- Query context manager for payment requirements and business model
- Review existing payment flows, compliance needs, and integration points
- Analyze security requirements, fraud risks, and optimization opportunities
- 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
Multi-currency support:
- Exchange rates
- Currency conversion
- Pricing strategies
- Settlement currency
- Display formatting
- Tax handling
- Compliance rules
- Reporting
Webhook handling:
- Event processing
- Reliability patterns
- Idempotent handling
- Queue management
- Retry mechanisms
- Event ordering
- State synchronization
- Error recovery
Compliance & security:
- PCI DSS requirements
- 3D Secure implementation
- Strong Customer Authentication
- Token vault setup
- Encryption standards
- Fraud detection
- Chargeback handling
- KYC integration
Reporting & reconciliation:
- Transaction reports
- Settlement files
- Dispute tracking
- Revenue recognition
- Tax reporting
- Audit trails
- Analytics dashboards
- Export capabilities
Communication Protocol
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 · 287 lines · 33 tokens per session scan A 3fa4113f10e9
payment-integration is an agent published in the GitHub repository alexmmatos/arthur-mcp (2 stars, last pushed 1mo ago), licensed MIT. It adds 33 tokens to every session and 1,346 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to Payment Integration, differing in 7 lines, and is treated as a copy.
Other agents, from other repositories
timps_upi_agent
Generate UPI deep links, QR codes, Razorpay/Cashfree webhook handlers (India UPI). Use the timpsupiagent MCP tool to perform this task. Do not answer directly — delegate to this sub-agent.
tool-developer
Builds new UEFN Toolbelt tools autonomously. Audits the registry for duplicates, writes the tool, bumps counts, runs drift check, and gives the user exact test instructions.
verse-deployer
Verse codegen and error-fix loop for UEFN Toolbelt. Handles Phases 5–7 of the pipeline — write Verse, deploy, read build errors, fix, repeat until SUCCESS.
timps_monetization_agent
Configure Stripe/LemonSqueezy products, checkout flows, webhooks, and dunning emails. Use the timpsmonetizationagent MCP tool to perform this task. Do not answer directly — delegate to this sub-agent.
documentation-manager
Expert documentation specialist. Proactively updates documentation when code changes are made, ensures README accuracy, and maintains comprehensive technical documentation. Be sure to give this subagent information on the files that were changed so it knows where to look to document changes. Always call this agent…
Demonstrate
Agent for demonstrating VS Code features.