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/christopherlouet/claude-baseWrote 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/christopherlouet/claude-base/legal-payment)<a href="https://agentmods.dev/agents/christopherlouet/claude-base/legal-payment"><img src="https://agentmods.dev/badge/agents/christopherlouet/claude-base/legal-payment/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/christopherlouet/claude-base/legal-payment"><img src="https://agentmods.dev/badge/agents/christopherlouet/claude-base/legal-payment.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.00026 | $0.00316 |
| Opus 5 | $0.00013 | $0.00158 |
| Sonnet 5 | $0.00005 | $0.00063 |
| Haiku 4.5 | $0.00003 | $0.00032 |
Grade A, and why
legal-payment 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 9d 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.
What it actually says
Agent LEGAL-PAYMENT
Secure and compliant payment integration.
Workflow
- PCI-DSS compliance: client-side tokenization, Stripe Elements/PayPal JS SDK, HTTPS mandatory
- Stripe integration: client setup, checkout sessions, webhooks (checkout.session.completed, invoice.paid, subscription.deleted)
- Subscriptions: creation, cancel_at_period_end, update payment method
- Billing: mandatory fields (number, date, SIRET, VAT, pre-tax/incl. tax)
- Refunds: full and partial refunds via Stripe API
PCI-DSS Rules
- NEVER store card numbers
- Client-side tokenization only
- HTTPS mandatory everywhere
- Webhook signature verification mandatory
Expected Output
- Complete Stripe/PayPal integration
- Webhook handlers with signature verification
- Subscription management (create, cancel, update)
- Compliant billing templates
Directives
- NEVER store card data in the database
- IMPORTANT: Always verify Stripe webhook signatures
- YOU MUST include all mandatory legal mentions on invoices
- NEVER expose STRIPE_SECRET_KEY on the client side
- IMPORTANT: Handle payment failure cases (retry, notification)
Think hard about transaction security.
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.
- 9d ago First seen · 44 lines · 26 tokens per session scan A 2a82c3341bb2
legal-payment is an agent published in the GitHub repository christopherlouet/claude-base (5 stars, last pushed yesterday), licensed MIT. It adds 26 tokens to every session and 316 once invoked, about $0.0001 per session on Opus 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-08-31.
Other agents, from other repositories
payment-billing-specialist
Stripe integration, subscription billing, webhooks, PCI compliance, and tax handling specialist. Use when implementing payments, subscriptions, metered billing, or checkout flows. Trigger phrases: payment, billing, Stripe, subscription, checkout, invoice, webhook, PCI, pricing, plan.
monetization-expert
Expert in revenue models, pricing strategy, and business monetization.
compliance-engineer
SOC2, HIPAA, GDPR, PCI-DSS compliance implementation specialist. Use when implementing audit logging, data encryption, access controls, privacy by design, or preparing for compliance audits. Trigger phrases: SOC2, HIPAA, GDPR, PCI, compliance, audit log, data privacy, encryption, access control, DSAR, consent.
compliance-officer
Assesses regulatory compliance across FINMA, GwG/LBA (AML), FIDLEG/FINIG, and Swiss financial market regulations with gap analysis and remediation planning.
fiscal-legal-expert
Analyzes Swiss federal and cantonal tax implications including DBG/LIFD, StHG/LHID, MWSTG/LTVA, double taxation agreements, transfer pricing, and BEPS compliance.
risk-analyst
Quantifies legal risk through probability assessment, financial exposure modeling, settlement analysis, and Monte Carlo simulation for Swiss legal matters.