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 daily-settlementgit 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/daily-settlement)<a href="https://agentmods.dev/skills/theyahia/wwmcp/daily-settlement"><img src="https://agentmods.dev/badge/skills/theyahia/wwmcp/daily-settlement/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/daily-settlement"><img src="https://agentmods.dev/badge/skills/theyahia/wwmcp/daily-settlement.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.00017 | $0.00438 |
| Opus 5 | $0.00009 | $0.00219 |
| Sonnet 5 | $0.00003 | $0.00088 |
| Haiku 4.5 | $0.00002 | $0.00044 |
Grade A, and why
daily-settlement 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
/daily-settlement — Chapa daily reconciliation
Algorithm
- Call
get_balance— this is the closing figure everything must tie back to. - Call
list_transactionswith pagination (page, per_page) and, if the user is chasing a specific bucket, status = pending | success | failed. - Page through with page until you reach today's boundary. This API paginates rather than filtering by date — do not claim a total you have not paged to.
- Call
list_transferswith the same pagination to get money going out. - Group inbound by status, sum successful amounts, sum charges (Chapa's fee) separately.
- Flag anything stuck: inbound still pending, or outbound transfers not in a final state.
For a stuck outbound, call
verify_transferwith its reference to get a fresh read.
Response format
## Chapa settlement — 2026-09-03
**Closing balance**: 42,300 ETB
### Inbound
| Status | Count | Amount |
|--------|-------|--------|
| success | 38 | 21,400 ETB |
| pending | 4 | 1,150 ETB |
| failed | 2 | 600 ETB |
Fees on successful: 748 ETB
### Outbound
3 transfers, 12,000 ETB — 1 pending (ref PAYOUT-02)
### Needs attention
- 4 inbound stuck in pending over 1 hour.
Notes
- Report only what the tools returned. Chapa does not expose a settlement report endpoint here, so this is reconstructed from listings — say so if the user needs an official one.
verify_transactiontakes a tx_ref if the user wants to drill into one inbound payment.
Examples
/daily-settlement
/daily-settlement 1 100
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 · 56 lines · 17 tokens per session scan A 6ce680355b8b
daily-settlement is a skill published in the GitHub repository theYahia/WWmcp (29 stars, last pushed 4d ago), licensed MIT. It adds 17 tokens to every session and 438 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.