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/Hainrixz/agente-pagokitWrote 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/hainrixz/agente-pagokit/migrate)<a href="https://agentmods.dev/commands/hainrixz/agente-pagokit/migrate"><img src="https://agentmods.dev/badge/commands/hainrixz/agente-pagokit/migrate/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/hainrixz/agente-pagokit/migrate"><img src="https://agentmods.dev/badge/commands/hainrixz/agente-pagokit/migrate.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.00021 | $0.00711 |
| Opus 5 | $0.00010 | $0.00356 |
| Sonnet 5 | $0.00004 | $0.00142 |
| Haiku 4.5 | $0.00002 | $0.00071 |
Grade A, and why
migrate 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 5d 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/pagokit:migrate
The common reasons are real ones: taxes became a burden and a merchant of record solves it; a local provider now covers the market better than the cross-border one; the current provider does not support a rail that customers keep asking for; or the provider is being wound down.
A migration is not a rewrite. It is a period where both run at once.
1. Establish what is actually in use
Read PAGOKIT_INTEGRATION.md, then verify against the code — it can be stale. Inventory:
- Which events are routed, and what each one does.
- Which customers have a stored payment method. These usually cannot move. Card tokens belong to the provider that vaulted them; some providers support a network token migration on request, most do not. Establish this before promising anything.
- Active subscriptions and their next billing dates.
- Anything referencing a provider id in the database.
2. State the constraints plainly, before planning
Read both providers' catalog entries and name the differences that will bite:
- Stored cards. If they cannot migrate, existing subscribers must re-enter a card. That is a churn event, not a technical detail, and the user needs to decide how to handle it.
- Event vocabulary. The two providers do not use the same event names. Map them
explicitly,
required_events_minimumtorequired_events_minimum, and flag anything with no equivalent. - Notification model. Moving to a
return_url_commitorping_then_pollprovider is a different architecture, not a swapped SDK. - Merchant of record. Moving to one means it becomes the seller of record. Invoices, tax handling and the name on the customer's statement all change.
- Refund semantics. If the new provider's rails include irreversible ones, the refund path changes shape.
3. Plan the coexistence
- Add the new provider alongside the old one (
/pagokit:adddoes this). - Route new payments to the new provider; leave existing subscriptions on the old one.
- Run both webhook handlers. Keep the old one alive for as long as the provider can still send disputes and refunds — that is months, not days.
- Migrate subscriptions at their natural renewal, not in a batch.
- Keep a
providercolumn on every payment row, forever. Historical reconciliation needs it long after the old provider is gone.
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.
- 5d ago First seen · 65 lines · 21 tokens per session scan A e9586b2fd113
migrate is a command published in the GitHub repository Hainrixz/agente-pagokit (46 stars, last pushed 8d ago), licensed MIT. It adds 21 tokens to every session and 711 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-09-04.
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-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…
financial-model
Generate a 6-year ecommerce financial model without writing the narrative business plan.
research
Professional equity research analysis with institutional-grade formatting.