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 method-specific-paymentgit 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/method-specific-payment)<a href="https://agentmods.dev/skills/theyahia/wwmcp/method-specific-payment"><img src="https://agentmods.dev/badge/skills/theyahia/wwmcp/method-specific-payment/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/method-specific-payment"><img src="https://agentmods.dev/badge/skills/theyahia/wwmcp/method-specific-payment.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.00024 | $0.00440 |
| Opus 5 | $0.00012 | $0.00220 |
| Sonnet 5 | $0.00005 | $0.00088 |
| Haiku 4.5 | $0.00002 | $0.00044 |
Grade A, and why
method-specific-payment 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 5d 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
/method-specific-payment — Force one payment method
Algorithm
- Call
get_payment_methods. It returns each enabled method with its id, name, key (fawry, visa, meeza, wallet…) and commission rate. - Match the method the user named to a row and take its numeric id. If the method they want is not in the list, stop — it is not enabled on this account. Do not substitute another.
- Show the commission rate for the chosen method before charging, so the user sees the cost.
- Call
send_paymentwith payment_method_id, cartTotal (a string), cartItems, successUrl, failUrl, and optionally currency and pendingUrl. - Call
get_invoice_datawith the returned invoice_id to confirm the outcome and pull the method-specific artifact — for Fawry that is the reference code the customer pays with.
Response format
## Fawaterak payment — fawry
**Method**: Fawry (id 2, commission 1.0%)
**Invoice**: 88231
**Total**: 450 EGP
**Status**: unpaid
**Fawry reference**: 187 264 913
Customer pays this reference at any Fawry outlet within 48 hours.
Notes
- Method ids are account-specific. Always read them from
get_payment_methods; never hardcode. - Wallet and Meeza flows return a redirect; Fawry returns a code. Present whichever the response actually contains.
- Commission differs per method — mention it when the user is choosing between rails.
Examples
/method-specific-payment fawry 450 "Mona Hassan" [email protected]
/method-specific-payment meeza 1200 "Ahmed Ali" [email protected]
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.
- 5d ago First seen · 48 lines · 24 tokens per session scan A 17d229869c7e
method-specific-payment is a skill published in the GitHub repository theYahia/WWmcp (29 stars, last pushed 4d ago), licensed MIT. It adds 24 tokens to every session and 440 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…