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 vp-woo-pont-checkout-order-datagit 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/vp-woo-pont-checkout-order-data)<a href="https://agentmods.dev/skills/lonsdale201/wp-agent-skills/vp-woo-pont-checkout-order-data"><img src="https://agentmods.dev/badge/skills/lonsdale201/wp-agent-skills/vp-woo-pont-checkout-order-data/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/vp-woo-pont-checkout-order-data"><img src="https://agentmods.dev/badge/skills/lonsdale201/wp-agent-skills/vp-woo-pont-checkout-order-data.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.00123 | $0.02017 |
| Opus 5.5 | $0.00049 | $0.00807 |
| Sonnet 5.5 | $0.00025 | $0.00403 |
| Haiku 4.5 | $0.00012 | $0.00202 |
Grade A, and why
vp-woo-pont-checkout-order-data 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 28d 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 — 162 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pickup-point checkout and order data
Use the plugin's point resolver, WooCommerce session, order object, and public hooks. Do not invent a second pickup-point field or infer the courier from a shipping label.
Edition boundary
Pickup-point import, map/search UI, the vp_pont shipping method, conditional pricing, classic checkout, Checkout Blocks, and canonical order storage are available without PRO. Carrier label generation and tracking are separate PRO workflows.
The 4.2.8 package requires WordPress 6.0 or newer and declares WooCommerce as a required plugin. Its Composer platform is PHP 7.4. The checkout/order contract was runtime-smoked on WordPress 7.1.2 and WooCommerce 11.1.2.
Canonical state
| Scope | Key | Shape and purpose |
|---|---|---|
| Woo session | selected_vp_pont |
Full selected-point array during cart/checkout. Treat it as ephemeral. |
| User meta | _vp_woo_pont_point_id |
Last preference as `provider |
| Order meta | _vp_woo_pont_provider |
Point-provider ID such as gls_locker, or a paired home-delivery carrier such as gls. |
| Order meta | _vp_woo_pont_point_id |
Provider-specific pickup-point ID. Its presence distinguishes point delivery from paired home delivery. |
| Order meta | _vp_woo_pont_point_name |
Display name captured at checkout. |
| Order meta | _vp_woo_pont_point_coordinates |
latitude;longitude. Parse defensively; do not treat it as an address. |
When a point is selected, update_order_with_selected_point() also replaces the WooCommerce shipping address with the point address. The point name becomes shipping company, while the shopper's name and phone remain on the order. Code that exports orders should therefore read both the point meta and the normal shipping address.
Use WC_Order methods so the integration remains HPOS-safe:
$order = wc_get_order( $order_id );
if ( ! $order instanceof WC_Order ) {
return;
}
$provider = VP_Woo_Pont_Helpers::get_provider_from_order( $order );
$carrier = VP_Woo_Pont_Helpers::get_carrier_from_order( $order );
$point_id = (string) $order->get_meta( '_vp_woo_pont_point_id' );
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.
- 28d ago First seen · 162 lines · 123 tokens per session scan A d9aa83ac8e76
vp-woo-pont-checkout-order-data is a skill published in the GitHub repository Lonsdale201/wp-agent-skills (24 stars, last pushed 4d ago), licensed MIT. It adds 123 tokens to every session and 2,017 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-27.
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…
commerce-app-api-mesh
Scaffold or update an Adobe API Mesh configuration (mesh.json) in front of a Commerce app: add GraphQL/OpenAPI sources, extend an existing Commerce GraphQL type with a new field, and wire a cross-source resolver for it. Use when the user mentions API Mesh, mesh.json, extending a Commerce GraphQL type (e.g. adding a…
doku-payment-gateway
Expert guide for integrating DOKU Payment Gateway: DOKU Checkout (Hosted & Modal Popup with HMAC-SHA256), Direct API SNAP BI Standard (VA, QRIS, Direct Debit with HMAC-SHA512), and Direct API Non-SNAP (Card Payment Page, OVO Push). Covers single-integration checkout, direct host-to-host APIs, webhook verification, and…
woocommerce-plugin-development
Create custom WooCommerce plugins using action/filter hooks, the Settings API, and REST API extensions to add features without modifying core.
webhook-integration
Dodo Payments webhook handling, covering endpoint setup, Standard Webhooks signature verification on the raw body, payment, subscription, and refund event types, idempotency with webhook-id, retries, and local testing. Use when receiving Dodo events, verifying webhook-signature headers, or syncing your database from…
better-auth-integration
Dodo Payments plugin for Better Auth (@dodopayments/better-auth) covering customer sync on signup, authenticated checkout, customer portal, usage ingestion, and verified webhooks. Use when an app uses Better Auth and needs the dodopayments, dodopaymentsClient, checkout, portal, usage, or webhooks plugins; for other…