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-health-check-processinggit 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-health-check-processing)<a href="https://agentmods.dev/skills/lonsdale201/wp-agent-skills/wcs-health-check-processing"><img src="https://agentmods.dev/badge/skills/lonsdale201/wp-agent-skills/wcs-health-check-processing/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-health-check-processing"><img src="https://agentmods.dev/badge/skills/lonsdale201/wp-agent-skills/wcs-health-check-processing.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.00090 | $0.02815 |
| Opus 5.5 | $0.00036 | $0.01126 |
| Sonnet 5.5 | $0.00018 | $0.00563 |
| Haiku 4.5 | $0.00009 | $0.00281 |
Grade A, and why
wcs-health-check-processing 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 — 196 lines — stays where its author put it; the contents beside it link to each section on GitHub.
WooCommerce Subscriptions: Health Check and processing reliability
Use this when debugging WCS 8.8+ subscription processing, missing renewal orders, stuck manual renewals, Health Check scan results, or low-traffic stores where Action Scheduler is not reliably processing subscription work.
Misconception this skill corrects
"If renewals are missing, create Action Scheduler rows or write
_schedule_next_paymentdirectly."
That can duplicate or desync WCS state. WCS 8.8 ships a Health Check scanner and Processing Reliability settings. Use the subscription object APIs, built-in Health Check tooling, and Action Scheduler configuration before inventing custom queue runners.
When to use this skill
Trigger when ANY of the following is true:
- The user mentions WooCommerce > Status > Subscriptions, Health Check, Resolve, missing renewals, automatic-renewal candidates, or scan/cancel scan.
- Code contains
wcs_health_check_candidates,wcs_health_check_runs,wcs-health-check,RemediationAdvisor,ToolRunner,CandidateStore,ScheduleManager, orStatusTab. - The store has renewal delays,
DISABLE_WP_CRON, low traffic, or asks about Dedicated processing / Web cron support. - Code contains
wcs_dedicated_queue_enabled,woocommerce_subscriptions_queue_rotation,wcs_external_trigger_rate_limit_window, or/subscriptions/job-queue.
Health Check surface
WCS registers the Health Check tab from Automattic\WooCommerce_Subscriptions\Internal\HealthCheck\Bootstrap during plugin init.
| Surface | Location / name | Notes |
|---|---|---|
| Admin tab | WooCommerce > Status > Subscriptions | StatusTab::TAB_SLUG is wcs-health-check. |
| Candidate table | {$wpdb->prefix}wcs_health_check_candidates |
Detected subscriptions per scan run. |
| Run table | {$wpdb->prefix}wcs_health_check_runs |
Scan run metadata and progress. |
| Log source | wcs-health-check |
Used for scan/remediation/table failures. |
| AJAX suggest | wp_ajax_wcs_health_check_suggest_remediation |
Nonce action wcs_health_check_suggest_remediation. |
| AJAX tool call | wp_ajax_wcs_health_check_tool_call |
Nonce action wcs_health_check_tool_call. |
| AJAX scan status | wp_ajax_wcs_health_check_scan_status |
Nonce action wcs_health_check_scan_status. |
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 · 196 lines · 90 tokens per session scan A 8b3cb27c3553
wcs-health-check-processing is a skill published in the GitHub repository Lonsdale201/wp-agent-skills (25 stars, last pushed 7d ago), licensed MIT. It adds 90 tokens to every session and 2,815 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-03.
Other skills, from other repositories
selling-partner-listing-troubleshooter
Top-level entry point for any 'something's wrong with my listing' question in the Selling Partner API (SP-API). Does a quick read of the listing's status and issues, identifies the symptom, and routes the seller to the right specialist skill. Use when the complaint is non-specific: 'something's wrong with my listing'…
gke-workload-scaling-troubleshooting
Diagnoses GKE HorizontalPodAutoscaler (HPA) failures — metrics showing as , FailedGetResourceMetric / FailedGetScale / FailedComputeMetricsReplicas events, missing Pod resource requests, custom/external metrics-pipeline breakage (FailedGetExternalMetric / FailedGetCustomMetric, unavailable metrics adapter…
comet-hotfix
Comet preset path: Bug fix / hotfix. Skip brainstorming, directly open → build → verify → archive. Applicable for behavior fixes, scenarios not involving new capability design.
reproduce-and-fix-issues
Reproduce triaged Slack bugs through a configured app-control adapter, verify existing fixes, and open a bounded draft pull request only after before-and-after proof. Use only from the configured Benny repro automation.
factory-lookback
Experimental workflow for auditing recurring feedback, telemetry, errors, and brittle delivery paths to find systemic fixes. Use for periodic or requested cross-source lookbacks, not routine single-item intake.
comet-hotfix
A quick workflow for fixing an existing bug in Comet, a tool that manages structured code changes. It moves through opening the change, building, checking, and archiving it.