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 theYahia/WWmcp --skill order-paymentsgit clone --depth 1 https://github.com/theYahia/WWmcpWrote 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/theyahia/wwmcp/order-payments)<a href="https://agentmods.dev/skills/theyahia/wwmcp/order-payments"><img src="https://agentmods.dev/badge/skills/theyahia/wwmcp/order-payments/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/theyahia/wwmcp/order-payments"><img src="https://agentmods.dev/badge/skills/theyahia/wwmcp/order-payments.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.00013 | $0.00474 |
| Opus 5 | $0.00006 | $0.00237 |
| Sonnet 5 | $0.00003 | $0.00095 |
| Haiku 4.5 | $0.00001 | $0.00047 |
Grade A, and why
order-payments 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 6d 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.
What it actually says
/order-payments — Order Payments
Algorithm
- Find the order:
list_orders(filter_number or filter_customer) orget_order(id, by:"id"/"externalId", detail:"full"). detail:"full" is what exposes the existing payments — the summary view does not. - Read the valid payment type codes with
list_payment_types. Never invent a code. - Register the payment with
order_payment_create(order_id or order_external_id, amount, type, optional status and paid_at as "YYYY-MM-DD HH:MM:SS"). - Correcting an amount, status or date on an existing payment:
order_payment_edit(id, by, amount / status / paid_at). Prefer editing over delete+recreate — it keeps the payment id stable. - Only remove a payment created in error:
order_payment_delete(id). This is destructive; confirm the payment id with the user first. - Re-read
get_orderwith detail:"full" and show the payment list plus the remaining balance.
Notes
- Multi-site accounts: pass the
siteparam, taking the code fromlist_sites, or the write is rejected. - amount is a plain number in the account currency.
- Under RETAILCRM_READONLY all three write tools are unavailable — report that rather than looking for a workaround.
Response Format
## Order #10432 — payments
**Order total**: 18,400 RUB
**Paid**: 10,000 RUB · **Remaining**: 8,400 RUB
| Payment | Type | Amount | Status | Paid at |
|---------|------|--------|--------|---------|
| 5512 | bank-card | 10,000 RUB | paid | 2026-08-19 14:02 |
Registered payment 5518: 8,400 RUB, type cash, status paid.
Examples
/order-payments 10432
/order-payments 10432 8400
/order-payments edit payment 5512 status paid
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.
- 6d ago First seen · 46 lines · 13 tokens per session scan A 023fc5aad9cf
order-payments is a skill published in the GitHub repository theYahia/WWmcp (29 stars, last pushed 5d ago), licensed MIT. It adds 13 tokens to every session and 474 once invoked, about $0.0001 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-06.
Other skills, from other repositories
lemonsqueezy
Operate Lemon Squeezy — the Merchant of Record for digital products and SaaS — via its JSON:API REST endpoints. Covers stores, products, variants, checkouts, orders, subscriptions, customers, and license keys. Use when the user wants MoR billing (EU VAT, chargebacks, sales tax all handled for 5% + fees) instead of…
stripe-link-cli
Agent payments via Stripe Link — cards, SPT, approvals.
stripe-best-practices
Guides Stripe integration decisions across development and test environment planning (separate sandboxes vs the shared test mode sandbox), API selection (Checkout Sessions vs PaymentIntents), Connect platform setup (Accounts v2, controller properties), billing/subscriptions, tax and registrations (Stripe Tax…
okx-cex-portfolio
This skill should be used when the user asks about 'account balance', 'how much USDT do I have', 'my funding account', 'show my positions', 'open positions', 'position P&L', 'unrealized PnL', 'closed positions', 'position history', 'realized PnL', 'account bills', 'transaction history', 'trading fees', 'fee tier'…
ai-slop
Operational rubric that turns "don't make AI slop" into observable properties, severity levels, evidence requirements, and repair actions for interface design. Use as the reference rubric when building or reviewing marketing sites, product interfaces, dashboards, portfolios, or e-commerce pages, especially alongside…
amazon-returns-recovery
Suede-affiliated Amazon money-recovery audit for restocking fees, short or denied refunds, and Amazon-billed subscriptions. Use when the user mentions a restocking fee, a short or denied Amazon refund, or a forgotten Prime Video Channel, Audible, Kindle Unlimited, or Prime charge, or asks whether Amazon still owes or…