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.
git clone --depth 1 https://github.com/moshcoder/moshcodeWrote 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/commands/moshcoder/moshcode/invoice)<a href="https://agentmods.dev/commands/moshcoder/moshcode/invoice"><img src="https://agentmods.dev/badge/commands/moshcoder/moshcode/invoice/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/commands/moshcoder/moshcode/invoice"><img src="https://agentmods.dev/badge/commands/moshcoder/moshcode/invoice.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00430 |
| Opus 5.5 | $0.00007 | $0.00172 |
| Sonnet 5.5 | $0.00003 | $0.00086 |
| Haiku 4.5 | $0.00002 | $0.00043 |
Grade A, and why
invoice 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 1mo 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
Task
Propose an invoice for $ARGUMENTS. Always dry-run first:
billing invoice new $ARGUMENTS --dry-run --json
Show the user what it would create. Only run it again without --dry-run when
they have said to.
Line items come from --from-timer (tracked hours), from --item "Description|quantity|price", or both on the same invoice.
Rules
- Creating an invoice is a business action. Do not write one unprompted.
--dry-runbuilds and validates the entire invoice — the rate lookup and the double-billing check included — so a dry run that succeeds means the real one will. There is no reason to skip it. - A new invoice is a draft.
billing invoice mark <n> sentis a separate, deliberate step and this tool never emails anything. Do not mark an invoice sent or paid unless the user asked. - Read
amounts(decimal) when talking to a person; the baretotalis in minor units. - Exit 3 on
--from-timermeans there were no unbilled hours. Checkbilling hoursand reportskipped.runningrather than concluding there is nothing to bill. - The same hour cannot reach two invoices: each invoice records the timer entry ids it covers. If the user wants to re-bill something, voiding the old invoice releases those hours.
- Prefer
billing invoice render <n> --format html --out <file>when they want something to send: it is one self-contained file that prints to PDF.
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.
- 1mo ago First seen · 40 lines · 17 tokens per session scan A 10d5d507bf8a
invoice is a command published in the GitHub repository moshcoder/moshcode (3 stars, last pushed 4d ago), licensed MIT. It adds 17 tokens to every session and 430 once invoked, about $0.0001 per session on Opus 5.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-31.
Other commands, from other repositories
valuation-methods
Valuation methods analysis — multiples, DCF inputs, PEG integration, valuation assumption extraction.
merit-reconcile
Preview or check the status of Stripe → Merit payout reconciliation (read-only).
cost-per-task
Compute cost-per-successful-task unit economics from usage and cost data, including retries, failures, and quality thresholds.
audit-checklist
Perform an internal audit, review controls, or prepare for an external financial audit.
scan
Scan AWS account for cost optimization.
audit
Scan for non-kernel money math. Rebuild critical flows as JournalEntrys. Replay and prove. Complements /ledger-verify.