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 skills add Hainrixz/agente-pagokit --skill subscription-lifecyclegit 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/skills/hainrixz/agente-pagokit/subscription-lifecycle)<a href="https://agentmods.dev/skills/hainrixz/agente-pagokit/subscription-lifecycle"><img src="https://agentmods.dev/badge/skills/hainrixz/agente-pagokit/subscription-lifecycle/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/skills/hainrixz/agente-pagokit/subscription-lifecycle"><img src="https://agentmods.dev/badge/skills/hainrixz/agente-pagokit/subscription-lifecycle.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00102 | $0.01251 |
| Opus 5.5 | $0.00041 | $0.00500 |
| Sonnet 5.5 | $0.00020 | $0.00250 |
| Haiku 4.5 | $0.00010 | $0.00125 |
Grade A, and why
subscription-lifecycle 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 1mo 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
subscription-lifecycle
Creating a subscription is one API call. Everything that follows is where the money is lost.
The state machine nobody draws
trialing ──► active ──► past_due ──► canceled
│ │ ▲ │
│ │ └─────────┘ (retry succeeded)
│ ▼
│ paused / grace
└──► canceled (trial abandoned)
past_due is the state that matters. A subscription there is still delivering value and no
longer being paid for. How long you tolerate that, and what the customer sees while it lasts,
is a product decision the code has to encode explicitly — the default of "keep serving forever
because nobody wrote the branch" is the expensive one.
Involuntary churn is the biggest line item
Most subscription cancellations are not decisions. They are expired cards, changed cards, and issuer declines on a merchant-initiated transaction. Concretely:
- Retry on a schedule, not immediately. Same-day retries mostly fail again. Spread them over days, and stop before the issuer starts treating you as abusive.
- Ask before it breaks. A card expiring next month is knowable this month.
- Use account updater where the provider offers it — the issuer tells them the new number.
- Distinguish soft from hard declines. "Insufficient funds" is worth retrying on payday. "Stolen card" is not worth retrying at all, and retrying it looks like testing stolen cards.
The stored-credential framework
The first charge is customer-initiated (CIT), with the customer present. Every later charge is merchant-initiated (MIT), and the networks require it to reference the original.
Persist the network transaction id from the first charge and send it on every subsequent one. Mastercard requires the stored Trace ID on economically-related MITs from 23 October 2026, and Visa's Original Transaction ID already drives approval rates today. An unlinked MIT is not a warning — it is a decline.
That means a column: network_transaction_id on the stored payment method or the subscription.
Read recurring.network_txn_id_required from the provider entry.
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.
- 1mo ago First seen · 111 lines · 102 tokens per session scan A b729b4a2443e
subscription-lifecycle is a skill published in the GitHub repository Hainrixz/agente-pagokit (65 stars, last pushed 1mo ago), licensed MIT. It adds 102 tokens to every session and 1,251 once invoked, about $0.0004 per session on Opus 5.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 skills, from other repositories
greybeard
Makes your AI agent defensive about the backend failure modes that page you at 3am. Before writing server-side code, the agent stops at a ladder of hard-won rules — money as integer minor-units, idempotent mutations, timeouts and backoff on every external call, explicit transaction boundaries, no N+1 queries…
enable-banking-api
Domain knowledge about the Enable Banking Open Banking API. Reference this when working with API-based bank sync.
add-cloud-flow
Integrates Power Automate cloud flows into a Power Pages site. Lists available flows, suggests relevant ones based on intent, identifies scenarios and web roles, creates metadata files, and generates client-side code to call flows. Handles both new flow registration and adding already-registered flows to additional…
list-connections
Lists Power Platform connections in the current environment. Use when you need a connection ID before adding a connector to a code app.
financial-statement-analysis
Reads a set of financial statements and establishes what changed and why — fluctuation analysis against prior period and against budget, profitability, liquidity, solvency and efficiency ratios, benchmarking, and the non-GAAP measures presented alongside them. Use this to interpret results, review a counterparty's or…
tidewave-integration
Tidewave MCP runtime tools — debugging, smoke testing, live state inspection, SQL queries, hex docs. Use when evaluating code in a running Phoenix app.