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 fluentcart-rest-headlessgit 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/fluentcart-rest-headless)<a href="https://agentmods.dev/skills/lonsdale201/wp-agent-skills/fluentcart-rest-headless"><img src="https://agentmods.dev/badge/skills/lonsdale201/wp-agent-skills/fluentcart-rest-headless/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/fluentcart-rest-headless"><img src="https://agentmods.dev/badge/skills/lonsdale201/wp-agent-skills/fluentcart-rest-headless.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.00113 | $0.01249 |
| Opus 5 | $0.00056 | $0.00624 |
| Sonnet 5 | $0.00023 | $0.00250 |
| Haiku 4.5 | $0.00011 | $0.00125 |
Grade A, and why
fluentcart-rest-headless 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 11d 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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
FluentCart REST and headless clients
Inventory the routes registered by the installed version before designing a client. FluentCart 1.6.0 registers its main REST API under /fluent-cart/v2, but not every browser checkout operation is a REST resource.
Read route-auth-map.md before exposing data or building a headless/mobile client.
Do not derive routes from generic examples
The official developer pages currently contain examples that alternate v1 and v2 and describe generic cart endpoints not registered by the tested 1.6.0 runtime. The main API is v2, while an isolated v1 editor-autosave route also exists; never rewrite a route's version globally. Use rest_get_server()->get_routes(), the installed route files, and controller code as the contract for a pinned version.
In 1.6.0, checkout/cart mutations also use authenticated or public WordPress AJAX dispatchers such as fluent_cart_checkout_routes and fluent_cart_place_order. There is no source/runtime-confirmed generic /fluent-cart/v2/cart/add, /cart/update, or /cart/remove family. A headless client must either reproduce the supported checkout transport precisely or add an addon-owned REST facade that delegates to the same server services.
Apply authentication and ownership separately
- Admin routes use FluentCart router policies/capabilities.
- Customer routes require an authenticated WordPress user, then controllers scope records to the resolved FluentCart customer.
- Public checkout/product/payment endpoints still require object-level checks, opaque identifiers, state validation, and abuse controls.
- A cart hash is a bearer pointer for cart continuity, not customer identity.
For same-origin JavaScript, use WordPress cookie authentication with a wp_rest nonce. For external trusted clients, WordPress Application Passwords provide Basic Auth over HTTPS. OAuth/JWT requires a separately installed and audited authentication provider; it is not supplied by FluentCart core.
What ships with it
2 files 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.
- 11d ago First seen · 128 lines · 113 tokens per session scan A e25cd5ddf20b
fluentcart-rest-headless is a skill published in the GitHub repository Lonsdale201/wp-agent-skills (22 stars, last pushed yesterday), licensed MIT. It adds 113 tokens to every session and 1,249 once invoked, about $0.0006 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-08-30.
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.