Update to Hostinger Connector

{
  "description": "Use when the user wants to see or manage what they pay Hostinger for — listing subscriptions and their renewal state, enabling or disabling auto-renewal, renewing a subscription, browsing the product catalog with prices, listing payment methods and setting a default, or placing an order for a Hostinger product. Every write here costs the user money or affects whether their services stay online.",
  "included_files": [],
  "name": "subscriptions-and-payments",
  "skill_md_contents": "---\nname: subscriptions-and-payments\ndescription: Use when the user wants to see or manage what they pay Hostinger for — listing subscriptions and their renewal state, enabling or disabling auto-renewal, renewing a subscription, browsing the product catalog with prices, listing payment methods and setting a default, or placing an order for a Hostinger product. Every write here costs the user money or affects whether their services stay online.\n---\n\n# Subscriptions and payments\n\nBinary: **`hostinger-billing-mcp`** — every tool named `billing_*`.\n\nRun the `hostinger` router first. Its safety gates apply here more than\nanywhere else in the product: **this is the only skill that can charge the\nuser's card.** Read the billable gate below before any write.\n\n## The reading half is safe — start there\n\n- `billing_getSubscriptionListV1` — every subscription on the account, with\n  status and renewal state. This is the answer to \"what am I paying for?\" and\n  \"when does X expire?\".\n- `billing_getCatalogItemListV1` — orderable products and prices. **Prices are\n  in cents**, as integers with no decimal point: `1099` is €10.99. Convert\n  before showing a price to the user, and never quote the raw integer.\n- `billing_getPaymentMethodListV1` — methods available for new orders. Show the\n  last digits and type; never echo full card data even if a field contains it.\n\nAnswer read-only questions from these three and stop. Do not offer a purchase the\nuser did not ask for.\n\n## The billable gate\n\n`billing_createPurchaseOrderV1` and `billing_renewSubscriptionV1` **place real\norders against a real payment method.** `billing_createPurchaseOrderV1` is the\nbroadest tool in the whole Hostinger catalog — it can order any product — which\nmakes it the one most likely to do expensive damage from a vague request.\n\nBefore either of them:\n\n1. `billing_getCatalogItemListV1` for the exact item and its price. Never order\n   an item the user named loosely — \"the cheapest plan\", \"whatever works\" — get\n   a specific catalog item first and read the name back.\n2. State **item, term and total in currency**, converted from cents, plus which\n   payment method will be charged from `billing_getPaymentMethodListV1`.\n3. **First confirmation** naming all of that, and saying that hosting and domain\n   purchases are generally non-refundable.\n4. **Second confirmation in a separate turn**, after the user answers the first.\n   Never batch several items into one approval, and never carry an approval\n   forward to a different item, term or quantity.\n\nNever place an order to unblock your own work. If a task stalls because a plan\nor a domain is missing, say so, quote what it would cost, and stop. \"Get my site\nonline\" is not authorisation to buy anything.\n\n## Auto-renewal — small calls, large consequences\n\n- `billing_enableAutoRenewalV1` — future charges will happen without asking.\n  Say that plainly and name the subscription and its renewal amount.\n- `billing_disableAutoRenewalV1` — **the service will expire at the end of the\n  current term.** For hosting that means the website goes offline; for a domain\n  it means the registration lapses and the name can be taken by someone else,\n  which is not reversible after the redemption window. Name the subscription and\n  the date it would lapse, and confirm.\n\nBoth are one confirmation, but the confirmation has to state the consequence, not\njust the toggle.\n\n## Payment methods\n\n- `billing_setDefaultPaymentMethodV1` — changes what future orders and renewals\n  charge. One confirmation naming the method.\n- `billing_deletePaymentMethodV1` — **check for dependencies first.** Removing\n  the method that active auto-renewals depend on means those renewals fail\n  silently and services lapse. Read `billing_getSubscriptionListV1` and\n  `billing_getPaymentMethodListV1`, say which subscriptions would be left without\n  a working method, and take two confirmations if any would.\n\nNever help the user *add* a payment method through these tools — there is no tool\nfor it, and card details must never pass through the conversation. Point them at\nhPanel.\n\n## Handling money data\n\nPrices are integer cents. Subscription and order responses may carry billing\nidentifiers and partial payment details. Show the user only what they asked for,\nnever write any of it into a project file or a commit, and never include it in a\nsummary that could be pasted elsewhere.\n\n## Full tool list\n\nReads: `billing_getSubscriptionListV1`, `billing_getCatalogItemListV1`,\n`billing_getPaymentMethodListV1`\n\nBillable: `billing_createPurchaseOrderV1`, `billing_renewSubscriptionV1`\n\nRenewal state: `billing_enableAutoRenewalV1`, `billing_disableAutoRenewalV1`\n\nPayment methods: `billing_setDefaultPaymentMethodV1`,\n`billing_deletePaymentMethodV1`\n"
}