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 month-end-closegit 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/month-end-close)<a href="https://agentmods.dev/skills/wellapp-ai/well/month-end-close"><img src="https://agentmods.dev/badge/skills/wellapp-ai/well/month-end-close/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/wellapp-ai/well/month-end-close"><img src="https://agentmods.dev/badge/skills/wellapp-ai/well/month-end-close.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.00064 | $0.00541 |
| Opus 5 | $0.00032 | $0.00270 |
| Sonnet 5 | $0.00013 | $0.00108 |
| Haiku 4.5 | $0.00006 | $0.00054 |
Grade A, and why
month-end-close 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 9d 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
Month-end close from Well
Closing is a repeatable checklist, not a heroic event — and every step has a manual fallback, because the day it breaks is the day it matters. The close is what produces the financials: once the period is reconciled and posted, the P&L, balance sheet, and tax figures fall out of it (see well:compte-de-resultat, well:balance-sheet, well:vat-summary).
The checklist
- Discover the schema first (see
well:querying-well-data) and fix the period (date range). - Bank reconciliation — every
transactionsrow in the period is matched to its invoice(s) or categorised; no unexplained movements. Usewell:reconciliation. Confirmaccount_balancesmatch the bank's closing balance. - Receivables / payables — open
invoicesreviewed; nothing miscoded; AR aging sane (well:ar-aging). - Posting status — every transaction and invoice in the period is posted to a journal entry (not left DRAFT). Query
journal_entriesfor the period and flag any source document with no posted entry — those are the gaps that block a clean close. - Balances — trial balance balances (total debits = total credits) across
ledger_accounts/journal_entries;account_balancesreconciled. - Tax — VAT/tax for the period computed from the now-posted ledger (
well:vat-summary).
Rules
- Report readiness, don't fake it. If anything is unreconciled, unposted, or unbalanced, list it as a blocker — do not declare the period closed.
- Each blocker should name the specific document/account and what's missing, so it's actionable.
- Incremental is fine: surface "N of M done, here are the M−N gaps" rather than all-or-nothing.
Present it
A checklist with pass/blocker per item, a list of specific gaps (each naming the document/account + what's needed), the trial-balance debits=credits check, and a clear verdict: ready to close or N blockers remain.
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.
- 9d ago First seen · 28 lines · 64 tokens per session scan A 903597d5eba7
month-end-close is a skill published in the GitHub repository WellApp-ai/Well (340 stars, last pushed 1mo ago), licensed MIT. It adds 64 tokens to every session and 541 once invoked, about $0.0003 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
lemon-squeezy
Lemon Squeezy simplifies global tax compliance and recurring billing. The official @lemonsqueezy/lemonsqueezy.js SDK handles interactions cleanly.
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.
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 /…