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 WellApp-ai/Well --skill reconciliationgit clone --depth 1 https://github.com/WellApp-ai/WellWrote 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/wellapp-ai/well/reconciliation)<a href="https://agentmods.dev/skills/wellapp-ai/well/reconciliation"><img src="https://agentmods.dev/badge/skills/wellapp-ai/well/reconciliation.svg" alt="Measured on agentmods" 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.00046 | $0.00436 |
| Opus 5 | $0.00023 | $0.00218 |
| Sonnet 5 | $0.00009 | $0.00087 |
| Haiku 4.5 | $0.00005 | $0.00044 |
Grade A, and why
reconciliation 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 8d 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
Reconciliation in Well
Goal: connect money movement (transactions) to commercial documents (invoices) and report what is matched, unpaid, or unexplained.
What Well already links
Well's pipelines maintain the link between a bank transaction and the invoice(s) it settles. Check the schema before computing matches by hand:
well_get_schema("invoice_transactions")— the join between invoices and transactions, if exposed. Querying this root is the fastest path to "which invoices are settled by which transactions".well_get_schema("invoices")— look for a payment-status / amount-paid / outstanding field and thegrand_total.well_get_schema("transactions")— amount, value/booking date, counterparty, and remittance fields.
Do this
- Unpaid invoices: query
invoicesfiltered on the payment-status / outstanding field the schema exposes (don't infer "unpaid" by subtracting sums if a status field exists). Sort by due date or amount. - Matched: read
invoice_transactions(or the link the schema shows) to list invoice ↔ transaction pairs. - Unmatched transactions:
transactionswith no linked invoice — candidates for manual review (could be fees, transfers, or a missing invoice). - When matching by hand (no link exposed), match on amount + date proximity + counterparty, never on amount alone.
Do NOT
- Do not declare an invoice paid purely because a transaction of the same amount exists — confirm via the link or counterparty + date.
- Do not sum across currencies without converting (see
exchange_rates).
Present it
Three buckets — Matched, Unpaid invoices, Unexplained transactions — each with counts and totals, plus the currency. Offer to drill into any bucket with well_get_entity.
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.
- 8d ago First seen · 33 lines · 46 tokens per session scan A 2516a5e8d966
reconciliation is a skill published in the GitHub repository WellApp-ai/Well (340 stars, last pushed 1mo ago), licensed MIT. It adds 46 tokens to every session and 436 once invoked, about $0.0002 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-08-30.
Other skills, from other repositories
paddle
Paddle acts as a Merchant of Record, meaning they handle sales tax (VAT, GST) calculations and remittance for you. Use the @paddle/paddle-node SDK to manage subscriptions and invoices.
stripe
Stripe provides APIs for payment processing, billing, subscriptions, and financial management. This skill focuses on the Stripe Node.js and Python SDKs, emphasizing PCI-compliant flows like Checkout Sessions and Webhook signatures.
lemon-squeezy
Lemon Squeezy simplifies global tax compliance and recurring billing. The official @lemonsqueezy/lemonsqueezy.js SDK handles interactions cleanly.
plaid
Plaid connects users' bank accounts to apps. This skill focuses on Plaid Link flow and the plaid-node SDK to extract transaction data.
dashboards
Use when creating or extending Costory dashboards, generating interesting FinOps overviews (suggestgroupby + suggestusagemetrics + text widgets), adding or replacing widgets, copying widgets between dashboards, editing dashboardContext (global filter / period / groupBy) via updatedashboard, or applying shared-context…
query
Use when exploring Costory cost, usage, metric, formula, budget, or external-metric data with the query tool — scope vs split (filterCel / groupBy), explorer PoP comparison, CEL discovery, unit economics, budgets. Not for one-shot "what changed last month" change trees — those use recipes explain-period-change /…