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 collect-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/collect-payment)<a href="https://agentmods.dev/skills/theyahia/wwmcp/collect-payment"><img src="https://agentmods.dev/badge/skills/theyahia/wwmcp/collect-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/collect-payment"><img src="https://agentmods.dev/badge/skills/theyahia/wwmcp/collect-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.00019 | $0.00454 |
| Opus 5 | $0.00010 | $0.00227 |
| Sonnet 5 | $0.00004 | $0.00091 |
| Haiku 4.5 | $0.00002 | $0.00045 |
Grade A, and why
collect-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
/collect-payment — Chapa checkout
Algorithm
- Collect amount (a string, e.g. "250"), email, first_name, last_name. Optional: phone_number, currency (defaults to ETB), callback_url, return_url, customization_title, customization_description.
- Generate tx_ref yourself if the user did not give one — it must be unique per attempt (e.g. order number plus timestamp). Reusing a tx_ref makes Chapa reject the request.
- Call
initialize_transactionwith those fields. It returns a checkout_url. - Send the customer to the checkout_url. Wait for them to finish — do not verify early, a fresh transaction reads as pending.
- Call
verify_transactionwith the same tx_ref. Read status, amount, charge (Chapa's fee), payment method and customer info from the response. - If status is pending after the customer says they paid, retry
verify_transactiononce after a short wait before treating it as failed.
Response format
## Chapa payment
**tx_ref**: ORDER-2026-0142-1725350400
**Amount**: 250 ETB
**Charge (fee)**: 8.75 ETB
**Status**: success
**Method**: telebirr
**Customer**: Abebe Kebede / [email protected]
Checkout link: https://checkout.chapa.co/checkout/payment/...
Notes
- amount is a string in this API. Pass "250", not 250.
- Chapa supports ETB and USD; anything else will be rejected.
- Never generate a tx_ref that collides with a previous one — verification keys off it.
Examples
/collect-payment 250 [email protected] Abebe Kebede
/collect-payment 1200 [email protected] Sara Tesfaye ORDER-991
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 · 51 lines · 19 tokens per session scan A 5d4e20c5421b
collect-payment is a skill published in the GitHub repository theYahia/WWmcp (29 stars, last pushed 4d ago), licensed MIT. It adds 19 tokens to every session and 454 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
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'…
pdf-invoice-extractor
OCR a PDF invoice with mistralocr and extract structured line-item data (vendor, date, amounts, VAT) for accounting reconciliation. Use when the user provides an invoice PDF to process.
french-invoice-reminder
Rédige une relance de facture B2B en français avec un ton contrôlé (poli, ferme, ou final). À utiliser quand l'utilisateur demande une relance facture, un rappel de paiement, un mail de recouvrement, ou une dunning letter en français.
invompt-local-beta-invoice
Create or manage an Invompt invoice, quote, estimate, or pro forma from natural-language intent in any language, including short follow-ups that reuse earlier facts. Use for explicit billing-document requests across Latin, Cyrillic, RTL, Indic, CJK, and Southeast Asian scripts. Do not use for price or budgeting advice…
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…
before-spend
Use this before any purchase, subscription, money transfer, or API credit top-up. Call sanctionauthorize first; never proceed when it returns false; if status is escalated, wait and follow handle-escalation.