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 Lonsdale201/wp-agent-skills --skill wcs-upgrade-compatibilitygit clone --depth 1 https://github.com/Lonsdale201/wp-agent-skillsWrote 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/lonsdale201/wp-agent-skills/wcs-upgrade-compatibility)<a href="https://agentmods.dev/skills/lonsdale201/wp-agent-skills/wcs-upgrade-compatibility"><img src="https://agentmods.dev/badge/skills/lonsdale201/wp-agent-skills/wcs-upgrade-compatibility/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/lonsdale201/wp-agent-skills/wcs-upgrade-compatibility"><img src="https://agentmods.dev/badge/skills/lonsdale201/wp-agent-skills/wcs-upgrade-compatibility.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.00120 | $0.02059 |
| Opus 5.5 | $0.00048 | $0.00824 |
| Sonnet 5.5 | $0.00024 | $0.00412 |
| Haiku 4.5 | $0.00012 | $0.00206 |
Grade A, and why
wcs-upgrade-compatibility 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Subscriptions upgrade compatibility
Ground changes in the installed release source and targeted runtime evidence. Use the changelog to identify work, then distinguish removed APIs, deprecated compatibility shims, changed defaults, security boundaries and bug fixes. Do not mechanically delete every deprecated name: migration notes must still identify what to replace.
Establish the comparison
Record WCS, WooCommerce, WordPress and PHP versions; authoritative order storage and synchronization; classic/Blocks checkout; gateways; and whether products use legacy subscription types or the subscription plans integrated since WCS 9.0. Read the release's full changelog, including intervening releases when upgrading from an older baseline.
Inventory the integration's hooks, settings reads/writes, template overrides, checkout/order-pay paths, plan IDs, order metadata and background actions. Separate public extension hooks from Internal classes. An indexed signature can lag a release: resolve disagreements against the exact installed source and record the evidence, rather than treating a missing lookup as removal.
Replace deprecated settings integration
| Deprecated surface | 9.2 behavior | Migration |
|---|---|---|
WC_Subscriptions_Admin::add_subscription_settings_tab() |
Still adds a tab but emits a notice. Core now registers a WC_Settings_Page through woocommerce_get_settings_pages. |
Remove companion code that registers WCS's own tab. Keep extension fields on established settings filters. |
WC_REST_Subscriptions_Settings |
Legacy mirror remains functional; autoloading the class itself emits deprecation. | Stop constructing or autoload-probing it. Use the existing /wc/v3/settings/subscriptions group. |
woocommerce_subscriptions_max_customer_suspension_range |
Deprecated callback still runs; its returned list is ignored. | Remove option-list logic. If overriding the effective limit, use pre_option_woocommerce_subscriptions_max_customer_suspensions with the canonical value contract. |
WCSG_Admin::get_gifting_option_text() / get_gifting_global_override_text() |
Describe a removed storewide default. | Remove consumers of those descriptions; use per-product gifting controls. |
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 94 lines · 120 tokens per session scan A 21eda0b26e56
wcs-upgrade-compatibility is a skill published in the GitHub repository Lonsdale201/wp-agent-skills (24 stars, last pushed 4d ago), licensed MIT. It adds 120 tokens to every session and 2,059 once invoked, about $0.0005 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-22.
Other skills, from other repositories
renewal-playbook
Crea un playbook de renovación estructurado para una cuenta de cliente. Úsalo cuando necesites planificar una renovación, estructurar una negociación de renovación, prepararte para una conversación de expansión, o construir una estrategia de renovación para cuentas en riesgo o saludables. Produce un brief de…
commerce-app-business-config
Manage custom business configuration in an Adobe Commerce app. Use when the user wants to add, modify, or remove merchant-configurable settings (config fields, admin config, store configuration) exposed through Commerce Admin. Creates typed config fields (text, password, email, url, tel, boolean, list) in…
acp
This page used to hold an archived copy of this skill. The archive now lives in the registry's data repository.
payment-gateway-expert
Expert guide for integrating payment gateways (Stripe, PayPal, Xendit, Midtrans, DOKU SNAP BI) and secure webhooks into SaaS platforms / Panduan ahli integrasi payment gateway dan webhook aman.
marketplace-purchase-vetting
Use this when the user asks whether a local listing is a scam, "too good to be true," worth looking at, or a good deal. Also use this when he asks you to find options — search/discover candidates, then vet the best ones. The goal is not a generic buying guide; it is a practical risk read with clear next steps.
agent-ready-mpp
Sub-skill: Implement MPP Payment Discovery. Publish OpenAPI with x-payment-info extensions so AI agents discover payable endpoints via Machine Payment Protocol (mpp.dev).