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/trust-entrygit clone --depth 1 https://github.com/protomated/protomated-plugins-officialWhat 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.00010 | $0.00617 |
| Opus 5 | $0.00005 | $0.00309 |
| Sonnet 5 | $0.00002 | $0.00123 |
| Haiku 4.5 | $0.00001 | $0.00062 |
Grade A, and why
trust-entry 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 2d 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 — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/legal-billing:trust-entry — Trust Account Entry
Record a trust deposit or withdrawal with compliance checks built in.
Invocation
/legal-billing:trust-entry $ARGUMENTS
Parse client name, direction (deposit or withdrawal), and amount from $ARGUMENTS. Ask for anything missing.
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 collect any fields yet. If connected, proceed; once you attempt add_trust_entry, if it 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 — Identify the entry type from $ARGUMENTS or ask:
- Deposit keywords: retainer, received, deposit, paid in, upfront, advance
- Withdrawal keywords: filing fee, disbursement, paid out, refund, cost advance, settlement payout
If unclear: "Is this a deposit into trust (money coming in) or a withdrawal (money going out)?"
Step 2 — Collect required fields:
- Client name — confirm spelling
- Amount — never $0 or negative
- Description — brief (e.g., "Retainer received", "Filing fee — Circuit Court")
- Date — default to today
- Matter name — ask if the client has multiple matters
Step 3 — Safety checks:
- If withdrawal > $10,000: "This is a $[X] withdrawal from trust. Please confirm you want to proceed."
- Double-check: for a deposit,
deposit= amount andwithdrawal= 0. For a withdrawal,withdrawal= amount anddeposit= 0. Never swap these.
Step 4 — Confirm before calling: "Recording a $[X] [deposit/withdrawal] for [client] — [description] on [date]. Confirm?"
Wait for explicit confirmation.
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.
- 2d ago First seen · 50 lines · 10 tokens per session scan A 9ec5c6730d61
trust-entry is a command published in the GitHub repository protomated/protomated-plugins-official (2 stars, last pushed 23d ago), licensed Apache-2.0. It adds 10 tokens to every session and 617 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
vat-registration-threshold
Use this workflow source as an internal runbook. Follow the tool order, safety rails, and approval gates below, but keep the user-facing response focused on the accounting task. Do not dump raw tool fields or compatibility-tool details to the user unless they are needed for a concrete choice.
monitor
AML transaction monitoring and suspicious activity reporting.
audit-checklist
Perform an internal audit, review controls, or prepare for an external financial audit.
tax-planning
Optimize tax liability or ensure tax compliance.
confronta
Forfettario vs SRL — quale conviene e quando ha senso passare. Confronto orientativo, mostra i poli e non un numero unico.
tax-advisor
Source-backed U.S. tax planning, document review, estimates, and international/Sweden guidance.