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/billing-reviewgit 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/billing-review)<a href="https://agentmods.dev/commands/protomated/protomated-plugins-official/billing-review"><img src="https://agentmods.dev/badge/commands/protomated/protomated-plugins-official/billing-review.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.1 | $0.00016 | $0.00432 |
| Opus 5 | $0.00008 | $0.00216 |
| Sonnet 5 | $0.00003 | $0.00086 |
| Haiku 4.5 | $0.00002 | $0.00043 |
Grade A, and why
billing-review 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 5d 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:billing-review — Weekly Billing Health Check
Pull a read-only snapshot of the attorney's billing position. No writes.
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 pull anything 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 dashboard:
Call get_dashboard. Present the summary clearly:
"📊 Billing Dashboard
- Total hours logged: [X]
- Total fees billed: $[X]
- Collected: $[X]
- Still unpaid: $[X]"
Step 2 — Pull unbilled entries:
Call get_time_entries with status: Unbilled. List any unbilled clients:
"Unbilled work (ready to invoice):
- [Client]: [hours] hrs — $[amount]
- ..."
If nothing is unbilled: "No unbilled work. You're all caught up."
Step 3 — Suggest actions: Based on what's outstanding, offer next steps:
- If unbilled entries exist: "Want me to invoice any of these? Say
/legal-billing:invoice-client [name]." - If unpaid invoices are aging: "You have $[X] in unpaid invoices. Want to follow up with a specific client?"
- If nothing outstanding: "Everything looks clean. Great week."
⚠️ Not legal advice — review before sending to client.
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.
- 5d ago First seen · 39 lines · 16 tokens per session scan A 4c567ba4a66d
billing-review is a command published in the GitHub repository protomated/protomated-plugins-official (2 stars, last pushed 2d ago), licensed Apache-2.0. It adds 16 tokens to every session and 432 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
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).
audit-checklist
Perform an internal audit, review controls, or prepare for an external financial audit.
scan
Scan AWS account for cost optimization.
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…
archive-ledger
../../../shared/commands/archive-ledger.md.