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-licensing-progit 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-licensing-pro)<a href="https://agentmods.dev/skills/lonsdale201/wp-agent-skills/fluentcart-licensing-pro"><img src="https://agentmods.dev/badge/skills/lonsdale201/wp-agent-skills/fluentcart-licensing-pro/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-licensing-pro"><img src="https://agentmods.dev/badge/skills/lonsdale201/wp-agent-skills/fluentcart-licensing-pro.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.00103 | $0.01246 |
| Opus 5 | $0.00051 | $0.00623 |
| Sonnet 5 | $0.00021 | $0.00249 |
| Haiku 4.5 | $0.00010 | $0.00125 |
Grade A, and why
fluentcart-licensing-pro 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 — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
FluentCart Pro licensing
This skill is Pro-only. Verify FluentCart Pro is active and the license module is enabled before using its models, routes, tables, or hooks.
Read licensing-protocol.md before extending generation, activation, update delivery, or client compatibility.
Configure products through the module
Use the Licensing module's product settings and LicenseManager/LicenseHelper services. Do not create keys or activation rows with ad-hoc SQL. The module relates licenses to customer, order, product, variation, subscription, sites, activations, and meta, and applies lifecycle rules to those relations.
Feature-detect ModuleSettings::isActive('license') and Pro classes after fluent_cart/init. A product being downloadable or subscription-based does not itself mean licensing is enabled for that variation.
Follow the commerce lifecycle
The built-in handler generates licenses after fluent_cart/order_paid for initial payment/subscription orders; extends validity on subscription renewal; reactivates where appropriate; and disables/expires/deletes licenses according to payment failure, full refund, validity expiry, order deletion, and module policy.
Listen to license-specific hooks for addon side effects instead of duplicating generation. Make extensions replay-safe: payment/webhook and repair flows may re-enter lifecycle code. Preserve the distinction among active, disabled, and expired plus the stored reason and previous status.
Do not revoke automatically on every transient renewal failure unless that is the explicit access policy. Subscription grace, next billing date, cancellation at period end, EOT, refund, and manual administration are separate decisions.
Treat credentials and activations as bearer authority
License keys and activation hashes are secrets. Never log them in full, expose them in public REST serializers, place them in analytics/referrers, or accept a license ID alone as authorization. Normalize the site URL through LicenseHelper and validate product/item binding on every check, activation, deactivation, version, and package request.
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 · 125 lines · 103 tokens per session scan A 4a84db0f4cfa
fluentcart-licensing-pro is a skill published in the GitHub repository Lonsdale201/wp-agent-skills (22 stars, last pushed yesterday), licensed MIT. It adds 103 tokens to every session and 1,246 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-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.