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 payout-to-bankgit 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/payout-to-bank)<a href="https://agentmods.dev/skills/theyahia/wwmcp/payout-to-bank"><img src="https://agentmods.dev/badge/skills/theyahia/wwmcp/payout-to-bank/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/payout-to-bank"><img src="https://agentmods.dev/badge/skills/theyahia/wwmcp/payout-to-bank.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.00021 | $0.00460 |
| Opus 5 | $0.00010 | $0.00230 |
| Sonnet 5 | $0.00004 | $0.00092 |
| Haiku 4.5 | $0.00002 | $0.00046 |
Grade A, and why
payout-to-bank 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
/payout-to-bank — Chapa transfer
Algorithm
- Call
get_balancefirst. If the available balance is below the payout amount, stop and report it — Chapa rejects underfunded transfers and the error is opaque. - Call
list_banks(currency defaults to ETB; pass USD if paying out in dollars). Find the bank the user named and take its bank_code. Never guess a bank_code. - Confirm account_name and account_number with the user, character by character. Transfers are not reversible from this API.
- Call
transferwith account_name, account_number, amount (a string), reference (unique per payout), bank_code, and optionally currency and beneficiary_name. - Call
verify_transferwith the same reference to read the final state. - If verification says pending, say pending. Do not report a payout as delivered on the strength of the transfer call alone.
Response format
## Chapa payout
**Balance before**: 42,300 ETB
**To**: Abebe Kebede / 1000123456789 / Commercial Bank of Ethiopia (bank_code 946)
**Amount**: 5,000 ETB
**Reference**: PAYOUT-2026-09-03-01
**Status**: success
Notes
list_banksis the only source of a valid bank_code — a wrong code silently routes to the wrong institution or fails late.- reference must be unique;
verify_transferlooks the transfer up by it. - amount is a string here as well.
Examples
/payout-to-bank 5000 "Abebe Kebede" 1000123456789 "Commercial Bank of Ethiopia" PAYOUT-01
/payout-to-bank 800 "Sara Tesfaye" 0123456789 Awash PAYOUT-02
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 · 48 lines · 21 tokens per session scan A b21792df7887
payout-to-bank is a skill published in the GitHub repository theYahia/WWmcp (29 stars, last pushed 4d ago), licensed MIT. It adds 21 tokens to every session and 460 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.