br-woo-routes

br-woo-routes is a skill for Claude Code, Codex from Lonsdale201/wp-agent-skills. It costs 70 tokens per session (2,737 once invoked), scanned A, original, MIT.

A route builder for exposing WooCommerce data through WordPress REST API endpoints, which let software exchange data with a site.

In plain words
What is it for?
Use it to expose orders, products, customers, and coupons through controlled API routes with selected actions and access rules.
Why use it?
It avoids writing the common listing, reading, creating, updating, deleting, permission, validation, and pagination logic for WooCommerce records.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to expose orders, products, customers, and coupons through controlled API routes with selected actions and access rules.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/lonsdale201/wp-agent-skills/br-woo-routes
Install

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.

Any agent
npx skills add Lonsdale201/wp-agent-skills --skill br-woo-routes
Clone the repo
git clone --depth 1 https://github.com/Lonsdale201/wp-agent-skills

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for br-woo-routes

README.md
[![agentmods](https://agentmods.dev/badge/skills/lonsdale201/wp-agent-skills/br-woo-routes/github.svg)](https://agentmods.dev/skills/lonsdale201/wp-agent-skills/br-woo-routes)
Your own site
<a href="https://agentmods.dev/skills/lonsdale201/wp-agent-skills/br-woo-routes"><img src="https://agentmods.dev/badge/skills/lonsdale201/wp-agent-skills/br-woo-routes/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.

agentmods 80×15 button for br-woo-routes

Your own site · 80×15
<a href="https://agentmods.dev/skills/lonsdale201/wp-agent-skills/br-woo-routes"><img src="https://agentmods.dev/badge/skills/lonsdale201/wp-agent-skills/br-woo-routes.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 70 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,737 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00070 $0.02737
Opus 5.5 $0.00028 $0.01095
Sonnet 5.5 $0.00014 $0.00547
Haiku 4.5 $0.00007 $0.00274

Measured 7d ago against content hash 560de11d7f7b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

br-woo-routes 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 7d 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.

better-route/br-woo-routes/SKILL.md · 258 lines

How it starts

The opening of the file, as written. The whole thing — 258 lines — stays where its author put it; the contents beside it link to each section on GitHub.

better-route: WooCommerce routes

Register Woo routes during rest_api_init and retain the returned Router when contracts are needed.

use BetterRoute\BetterRoute;

add_action('rest_api_init', static function (): void {
    $woo = BetterRoute::wooRouteRegistrar()->register('myapp/v1', [
        'basePath' => 'woo',
        'requireHpos' => true,
        'deleteMode' => 'trash',
        'actions' => [
            'customers' => ['list', 'get'],
            'coupons' => [],
        ],
        'permissions' => [
            'orders.list' => 'manage_woocommerce',
            'orders.create' => 'manage_woocommerce',
        ],
    ]);
});

Routes cover orders, products, customers, and coupons under /wp-json/myapp/v1/woo by default.

Actions and permissions

Each resource supports list, get, create, update, and delete; update registers both PUT and PATCH.

  • Omit actions.<resource> for full CRUD.
  • Pass [] to disable that resource.
  • Invalid action names or a non-array value throw.

Permission keys use <resource>.<action>. A value may be bool, capability string, any-of capability list, or callable receiving the request and optionally the registrar. Unrecognized/empty rules deny. Defaults are manage_woocommerce.

Customer writes also enforce native user capabilities inside the service:

  • create: create_users;
  • update: edit_user for the target;
  • delete: delete_user for the target.

Customer visibility defaults to the customer role and uses one CustomerRolePolicy for lists, detail and mutations. Configure additional customer-like roles explicitly:

'customerRoles' => new \BetterRoute\Integration\Woo\CustomerRolePolicy(
    allowedRoles: ['customer', 'wholesale_customer'],
    excludedRoles: ['former_customer'],
    allowPrivilegedRoles: false
),

Privileged roles, direct administrative capabilities and multisite superadmins are excluded by default, including multi-role accounts. Request role filters can only narrow the configured allowlist. allowPrivilegedRoles: true is a trusted server opt-in; it does not grant native user-write capabilities or make a user directory.

Read the full file on GitHub · 258 lines

Changes

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.

  1. 7d ago Changed · +51 lines · -18 tokens per session 560de11d7f7b
  2. 1mo ago Changed · +14 lines · -3 tokens per session 1067e5715795
  3. 1mo ago First seen · 193 lines · 91 tokens per session scan A c6feb894bb14

Subscribe to this mod's changes

br-woo-routes is a skill published in the GitHub repository Lonsdale201/wp-agent-skills (25 stars, last pushed 7d ago), licensed MIT. It adds 70 tokens to every session and 2,737 once invoked, about $0.0003 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-08-30.

Related

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…

adobe/skills · 80 tokens

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…

adobe/skills · 100 tokens

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…

roedyrustam/vibes-plug · 107 tokens

woocommerce-plugin-development

Create custom WooCommerce plugins using action/filter hooks, the Settings API, and REST API extensions to add features without modifying core.

finsilabs/awesome-ecommerce-skills · 28 tokens

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…

dodopayments/skills · 72 tokens

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…

dodopayments/skills · 82 tokens