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-rest-apigit 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-rest-api)<a href="https://agentmods.dev/skills/lonsdale201/wp-agent-skills/wcs-rest-api"><img src="https://agentmods.dev/badge/skills/lonsdale201/wp-agent-skills/wcs-rest-api/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-rest-api"><img src="https://agentmods.dev/badge/skills/lonsdale201/wp-agent-skills/wcs-rest-api.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.00106 | $0.02684 |
| Opus 5 | $0.00053 | $0.01342 |
| Sonnet 5 | $0.00021 | $0.00537 |
| Haiku 4.5 | $0.00011 | $0.00268 |
Grade A, and why
wcs-rest-api 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 — 218 lines — stays where its author put it; the contents beside it link to each section on GitHub.
WooCommerce Subscriptions REST API
Use the latest wc/v3 controllers for new admin/server integrations. WCS also registers v1/v2 and a legacy WC API for compatibility; do not choose them for new work.
API boundary
The WCS REST API is an authenticated store-management API. It is not a shopper-facing subscription-management API and it is not the Woo Store API.
- Server/admin API:
/wp-json/wc/v3/subscriptions... - Shopper cart/checkout API:
/wp-json/wc/store/v1... - APFS plan management: authenticated
wc/v3routes
Never expose Woo consumer secrets in a browser or mobile app. A customer portal needs your own authenticated REST controller that checks subscription ownership/capabilities and calls WCS domain methods.
Route map
WCS 9.0 registers:
| Method | Route | Purpose |
|---|---|---|
GET, POST |
/wc/v3/subscriptions |
List/create subscriptions. |
GET, PUT, PATCH, DELETE |
/wc/v3/subscriptions/<id> |
Read/update/delete one subscription. |
POST |
/wc/v3/subscriptions/batch |
Batch create/update/delete. |
GET |
/wc/v3/subscriptions/statuses |
Public status labels; no subscription data. |
GET |
/wc/v3/subscriptions/<id>/orders |
Related parent/renewal/switch/resubscribe orders. |
GET, POST |
/wc/v3/orders/<order_id>/subscriptions |
Read subscriptions for an order or create them from eligible order items. |
| REST note methods | /wc/v3/subscriptions/<id>/notes[/<note_id>] |
Subscription notes. |
Plan routes are separate:
/wc/v3/subscriptions/storewide-plans/wc/v3/products/<product_id>/subscription-plans
Use wcs-subscription-plans-apfs for plan payloads. A subscription resource is not a plan resource.
Authentication and permissions
Use WooCommerce REST authentication over HTTPS or trusted WordPress application authentication. Controllers inherit Woo order permission checks; write operations require suitable order-management capabilities.
The statuses route intentionally permits public reads because it contains labels only. Do not infer that subscription collection/item routes are public.
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 · 218 lines · 106 tokens per session scan A 69086b94545a
wcs-rest-api is a skill published in the GitHub repository Lonsdale201/wp-agent-skills (22 stars, last pushed 2d ago), licensed MIT. It adds 106 tokens to every session and 2,684 once invoked, about $0.0005 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.