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/commands/christopherlouet/claude-base/legal-payment)<a href="https://agentmods.dev/commands/christopherlouet/claude-base/legal-payment"><img src="https://agentmods.dev/badge/commands/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/commands/christopherlouet/claude-base/legal-payment"><img src="https://agentmods.dev/badge/commands/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.00000 | $0.00496 |
| Opus 5.5 | $0.00000 | $0.00198 |
| Sonnet 5.5 | $0.00000 | $0.00099 |
| Haiku 4.5 | $0.00000 | $0.00050 |
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 22d 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.
How it starts
The opening of the file, as written. The whole thing — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PAYMENT Agent
Payment integration and subscription management.
Request context
$ARGUMENTS
Objective
Integrate a complete payment system with checkout, webhooks, subscription management and legal compliance.
Workflow
- Analyze the needs (one-shot, subscription, usage-based, B2B/B2C)
- Choose the right provider (Stripe, Paddle, LemonSqueezy)
- Implement the checkout (session, redirection, success/cancel)
- Configure essential webhooks (checkout.session.completed, checkout.session.async_payment_succeeded for delayed methods, invoice.paid, customer.subscription.updated/deleted)
- Handle subscription states and feature access logic
- Configure the Customer Portal (invoices, payment, plan change, cancellation)
- Test with test cards and Stripe CLI
- Verify security (webhook signature, HTTPS, no client-side prices)
Expected output
- Architecture chosen (provider, type, integration)
- Plans to create with prices and features
- Webhooks to implement with actions
- Code ready-to-use implementation
- Checklist for launch (products, webhooks, portal, tests, live mode)
Related agents
| Agent | Usage |
|---|---|
/legal:legal-docs |
Terms of sale and legal notices |
/legal:legal-rgpd |
Payment data compliance |
/qa:qa-security |
Transaction security |
/biz:biz-pricing |
Define the pricing strategy |
IMPORTANT: Always use webhooks - never trust the checkout return alone.
YOU MUST verify the webhook signature.
NEVER store card numbers - use Stripe.js/Elements.
Think hard about edge cases (failed payment, downgrade, refund).
See also
If the project uses Stripe, Stripe's own stripe-best-practices skill (stripe/ai, MIT, pin 9a33771f) goes deeper: Checkout Sessions vs PaymentIntents, billing and subscriptions, Stripe Tax, Connect, deprecated-API migrations, API key handling. It is Stripe-scoped by nature (it routes new usage-based billing to Metronome, a Stripe product); the provider choice stays in this command. Recipe: docs/recipes/recommended-vendor-skills.md §"Stack-specific".
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.
- 22d ago Changed · +4 lines 7116accaa446
- 1mo ago First seen · 50 lines · 0 tokens per session scan A 599ce759fbf5
legal-payment is a command published in the GitHub repository christopherlouet/claude-base (5 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 496 tokens. 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-09-03.
Other commands, from other repositories
context-stats
Display context window usage and token statistics.
cancel-ralph
Cancel active Ralph Wiggum loop.
list-skills
Browse available skills by domain or list all skills with comprehensive categorization.
validate
Comprehensive validation for this codebase.
ultimate_validate_command
Generate comprehensive validation command for this codebase.
t_metaprompt_workflow
Based on the High Level Prompt follow the Workflow, to create a new prompt in the Specified Format. Before you start, WebFetch everything in the Documentation.