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 agentmods add commands/protomated/protomated-plugins-official/invoice-clientgit clone --depth 1 https://github.com/protomated/protomated-plugins-officialWrote 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/protomated/protomated-plugins-official/invoice-client)<a href="https://agentmods.dev/commands/protomated/protomated-plugins-official/invoice-client"><img src="https://agentmods.dev/badge/commands/protomated/protomated-plugins-official/invoice-client.svg" alt="Measured on agentmods" 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 | $0.00013 | $0.00480 |
| Opus 5 | $0.00006 | $0.00240 |
| Sonnet 5 | $0.00003 | $0.00096 |
| Haiku 4.5 | $0.00001 | $0.00048 |
Grade A, and why
invoice-client 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 3d 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
/legal-billing:invoice-client — Invoice a Client
End-to-end invoice flow: show unbilled work, confirm, then mark as billed.
Invocation
/legal-billing:invoice-client $ARGUMENTS
$ARGUMENTS should be the client name. If missing, ask: "Which client are you invoicing?"
Workflow
Step 0 — Confirm setup first: Call connect_google with check_only: true. If not connected, stop and tell the attorney to say "connect Google" — do not ask for a client name yet. If connected, proceed; if the first data call below returns "No Google Sheet configured yet", stop and ask whether to create a new sheet from the template (create_billing_sheet, only after they confirm) or connect an existing one (set_spreadsheet_url). Only continue once both are confirmed. If you call create_billing_sheet, always paste the full sheet URL from its result into your reply — do not just say "sheet created."
Step 1 — Pull unbilled entries:
Call get_time_entries with clientName and status: Unbilled.
If no unbilled entries: "No unbilled time found for [client]. Nothing to invoice." Stop here.
Step 2 — Show what will be invoiced: "Here's what I'll mark as billed for [client]:
| Date | Matter | Hours | Rate | Fee |
|---|---|---|---|---|
| [row] | ... | ... | ... | $... |
Total: $[X] across [N] entries.
Ready to mark all of these as billed with today's invoice date?"
Step 3 — Wait for confirmation, then call mark_billed.
Step 4 — Report success: "✅ Done. All [N] entries for [client] marked as Billed — invoice date set to today ([date]). ⚠️ Not legal advice — review before sending to client."
Step 5 — Preview invoice (optional): "Want me to pull the invoice preview? Say 'show invoice' and I'll read the Invoice tab."
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.
- 3d ago First seen · 47 lines · 13 tokens per session scan A 0a148c062dcb
invoice-client is a command published in the GitHub repository protomated/protomated-plugins-official (2 stars, last pushed 24d ago), licensed Apache-2.0. It adds 13 tokens to every session and 480 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-08-31.
Other commands, from other repositories
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
merit-reconcile
Preview or check the status of Stripe → Merit payout reconciliation (read-only).
valuation-methods
Valuation methods analysis — multiples, DCF inputs, PEG integration, valuation assumption extraction.
scan
Scan AWS account for cost optimization.
audit-checklist
Perform an internal audit, review controls, or prepare for an external financial audit.
finops-status
Orientation — say where an opportunity or assignment sits in the five-step FinOps lifecycle and what unlocks next. Useful when a record has no active stage: an opportunity while its assignments do the work, an assignment whose plan has not been approved yet, or a rejected or archived assignment. Read-only; mutates…