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-renewal-schedulergit 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-renewal-scheduler)<a href="https://agentmods.dev/skills/lonsdale201/wp-agent-skills/wcs-renewal-scheduler"><img src="https://agentmods.dev/badge/skills/lonsdale201/wp-agent-skills/wcs-renewal-scheduler/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-renewal-scheduler"><img src="https://agentmods.dev/badge/skills/lonsdale201/wp-agent-skills/wcs-renewal-scheduler.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.00085 | $0.03794 |
| Opus 5 | $0.00043 | $0.01897 |
| Sonnet 5 | $0.00017 | $0.00759 |
| Haiku 4.5 | $0.00009 | $0.00379 |
Grade A, and why
wcs-renewal-scheduler 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 9d 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 — 294 lines — stays where its author put it; the contents beside it link to each section on GitHub.
WooCommerce Subscriptions: renewal scheduler
Use this when code touches renewal timing, scheduled payments, renewal order creation, or retry behavior. The key rule: change subscription dates/status through WC_Subscription methods, not by writing schedule meta or Action Scheduler rows directly.
Misconception this skill corrects
"To reschedule a subscription, update
_schedule_next_paymentor callas_schedule_single_action()."
That bypasses WCS validation and the scheduler's cleanup/reschedule behavior. WCS_Scheduler listens to woocommerce_subscription_date_updated, woocommerce_subscription_date_deleted, and woocommerce_subscription_status_updated. Those fire when you use WC_Subscription::update_dates(), delete_date(), or update_status().
When to use this skill
Trigger when ANY of the following is true:
- The user wants to change
next_payment,trial_end,end,payment_retry, or renewal timing. - Code contains
_schedule_next_payment,_schedule_payment_retry,as_schedule_single_action,woocommerce_scheduled_subscription_payment,WCS_Action_Scheduler,wcs_create_renewal_order, orWCS_Retry_Manager. - A gateway or integration needs to charge recurring payments, create renewal orders, react after a renewal succeeded, or handle failed renewal retries.
Renewal flow
For a normal WCS-managed automatic renewal:
- A future Action Scheduler action exists in group
wc_subscription_scheduled_event. - The action hook is
woocommerce_scheduled_subscription_paymentwith argsarray( 'subscription_id' => $id ). WC_Subscriptions_Manager::prepare_renewal()runs at priority1. It puts the subscription on hold and creates a renewal order withwcs_create_renewal_order().wcs_renewal_order_createdfires after the renewal relation is stored.WC_Subscriptions_Payment_Gateways::gateway_scheduled_subscription_payment()runs at priority10.- For non-manual gateways that do not manage their own schedule, WCS triggers
woocommerce_scheduled_subscription_payment_{gateway_id}with$amount, $renewal_order. - After payment result, use
woocommerce_subscription_renewal_payment_completeorwoocommerce_subscription_renewal_payment_failedfor business side effects.
What ships with it
1 file 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.
- 9d ago First seen · 294 lines · 85 tokens per session scan A d77ec4b1837f
wcs-renewal-scheduler is a skill published in the GitHub repository Lonsdale201/wp-agent-skills (22 stars, last pushed 2d ago), licensed MIT. It adds 85 tokens to every session and 3,794 once invoked, about $0.0004 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-03.
Other skills, from other repositories
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…
doku-payment-gateway
Expert guide for integrating DOKU Payment Gateway (Jokul API v2). Covers HMAC-SHA256 header signature calculation, Checkout & Direct APIs (VA, QRIS, E-Wallet, Credit Card), webhook notification verification, and sandbox/production setup / Panduan ahli integrasi DOKU Payment Gateway.
webhook-integration
Complete guide for setting up and handling Dodo Payments webhooks for real-time payment event notifications.
better-auth-integration
Guide only for applications using @dodopayments/better-auth, covering authenticated customer sync, checkout, portal access, usage ingestion, and verified webhook callbacks.
newebpay-checkout
A checkout integration for NewebPay’s MPG payment service, which provides an online payment page. It includes encrypted payment data, an HTML form submission, and callback endpoints for payment results.
kryptogo-pay-webhook
A callback endpoint for KryptoGO Payment, which sends your application updates about a payment. It handles pending, successful, expired, insufficient, and refunded outcomes.