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 compte-de-resultatgit 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/compte-de-resultat)<a href="https://agentmods.dev/skills/wellapp-ai/well/compte-de-resultat"><img src="https://agentmods.dev/badge/skills/wellapp-ai/well/compte-de-resultat/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/compte-de-resultat"><img src="https://agentmods.dev/badge/skills/wellapp-ai/well/compte-de-resultat.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.00055 | $0.00555 |
| Opus 5 | $0.00028 | $0.00278 |
| Sonnet 5 | $0.00011 | $0.00111 |
| Haiku 4.5 | $0.00006 | $0.00056 |
Grade A, and why
compte-de-resultat 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 10d 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.
How it starts
The opening of the file, as written. The whole thing — 31 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Compte de résultat (P&L) from Well
A correct income statement comes from the posted accounting ledger, not from raw invoices. Well's sync/posting pipelines post invoices and bank transactions into journal_entries against ledger_accounts; that posted data already handles classification, accruals, and settlement that a raw-invoice sum misses.
Do this
- Discover the schema first (see
well:querying-well-data):well_get_schema("ledger_accounts")— the chart of accounts. Look for the account code/number and name/type fields; income-statement accounts are the revenue and expense classes (in a French plan comptable, classe 7 = produits, classe 6 = charges).well_get_schema("journal_entries")andwell_get_schema("journal_entry_lines")if present — the posted movements with debit/credit amounts and the date you'll filter the period on.
- Scope the period with a
whereClauseon the posting/entry date (e.g._gtestart,_lteend). - Aggregate by account: sum the posted amounts per ledger account, then group revenue accounts and expense accounts.
- Net result = total produits (revenue) − total charges (expenses).
Do NOT
- Do not reconstruct the P&L by summing issued invoices as revenue and received invoices as expenses. That misses postings, non-invoice entries, accruals, and account classification, and double-counts or omits settlement. Use the ledger.
- Do not hardcode account codes you haven't confirmed from
well_get_schema/the data — read the chart of accounts first.
If the ledger is empty
If journal_entries / ledger_accounts return no rows for the workspace, the books may not be posted yet. Say so explicitly, and only then offer an invoice-based approximation — clearly labelled as an estimate, not the compte de résultat — built from invoices (issued = revenue proxy, received = expense proxy) over the period.
Present it
Group the output as: Produits (revenue) lines → total; Charges (expense) lines → total; Résultat net. Note the currency and the period. Offer a month-by-month or category breakdown as a follow-up.
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.
- 10d ago First seen · 31 lines · 55 tokens per session scan A 47bb98de0601
compte-de-resultat is a skill published in the GitHub repository WellApp-ai/Well (341 stars, last pushed today), licensed MIT. It adds 55 tokens to every session and 555 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.
plaid
Plaid connects users' bank accounts to apps. This skill focuses on Plaid Link flow and the plaid-node SDK to extract transaction data.
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.
braintree
Braintree (by PayPal) provides enterprise payment processing accepting Credit Cards, PayPal, Venmo, Apple Pay, and Google Pay with PCI-compliant Hosted Fields and Drop-in UI.
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…