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 commands/ashikparvez89/larouex-fullstack-plugin/add-stripegit clone --depth 1 https://github.com/Ashikparvez89/larouex-fullstack-pluginWrote 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/ashikparvez89/larouex-fullstack-plugin/add-stripe)<a href="https://agentmods.dev/commands/ashikparvez89/larouex-fullstack-plugin/add-stripe"><img src="https://agentmods.dev/badge/commands/ashikparvez89/larouex-fullstack-plugin/add-stripe.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 | $0.00000 | $0.00129 |
| Opus 5 | $0.00000 | $0.00064 |
| Sonnet 5 | $0.00000 | $0.00026 |
| Haiku 4.5 | $0.00000 | $0.00013 |
Grade A, and why
add-stripe 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
100% identical to add-stripe — 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
Integrate Stripe payment processing. Set up Stripe account and obtain API keys. Implement checkout flow using Stripe Checkout or Payment Element. Create payment API endpoints in Azure Functions or Express. Add webhook handling for payment events: succeeded, failed, refunded. Implement subscription billing with recurring payments if needed. Handle payment failures with retry logic. Add receipt generation and email delivery. Ensure PCI compliance by never storing card details. Implement 3D Secure authentication (SCA) for European customers. Add payment method management for saved cards. Create payment history dashboard. Reference azure-serverless-agent or devops-railway-agent for backend integration. Test with Stripe test mode.
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 · 2 lines · 0 tokens per session scan A fa009432a853
add-stripe is a command published in the GitHub repository Ashikparvez89/larouex-fullstack-plugin (3 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 129 tokens. A static security scan graded it A with 0 findings. It is 100% identical to add-stripe, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
add-checkout
Create comprehensive shopping cart and checkout flow. Implement cart state management with Context API or Zustand. Create cart UI component with item list, quantity controls, and remove buttons. Calculate totals including subtotal, tax, shipping, and discounts. Add shipping address form with validation. Implement…
add-stripe
Integrate Stripe payment processing. Set up Stripe account and obtain API keys. Implement checkout flow using Stripe Checkout or Payment Element. Create payment API endpoints in Azure Functions or Express. Add webhook handling for payment events: succeeded, failed, refunded. Implement subscription billing with…
add-admin-panel
Create basic admin dashboard with protected routes. Implement admin route protection with role-based access control. Create dashboard layout with sidebar navigation using Bootstrap. Add user management table with search and pagination. Implement CRUD operations for users: create, read, update, delete. Add role…
add-api-azure
Create a new Azure Function HTTP endpoint with full integration.
add-auth
Implement authentication system with comprehensive user management.
add-charts
Integrate Chart.js or Recharts for data visualization. Create reusable chart components: line, bar, pie, area, scatter. Implement responsive sizing with container-based dimensions. Add interactive tooltips showing detailed data on hover. Create customizable legends with click-to-hide series. Support real-time data…