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/teamtinvio/jaz-aiWrote 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/teamtinvio/jaz-ai/jaz-payment-run)<a href="https://agentmods.dev/commands/teamtinvio/jaz-ai/jaz-payment-run"><img src="https://agentmods.dev/badge/commands/teamtinvio/jaz-ai/jaz-payment-run/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/teamtinvio/jaz-ai/jaz-payment-run"><img src="https://agentmods.dev/badge/commands/teamtinvio/jaz-ai/jaz-payment-run.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.00020 | $0.00323 |
| Opus 5 | $0.00010 | $0.00161 |
| Sonnet 5 | $0.00004 | $0.00065 |
| Haiku 4.5 | $0.00002 | $0.00032 |
Grade A, and why
jaz-payment-run 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.
What it actually says
Payment Run
Execute a batch payment run via clio jobs payment-run. Identifies outstanding bills and processes payments.
Usage
/jaz-payment-run due before 2025-02-28
/jaz-payment-run all overdue bills
Workflow
1. Generate the blueprint
clio jobs payment-run --due-before 2025-02-28 --json
2. Review outstanding bills
The blueprint lists all unpaid/overdue bills matching the criteria, grouped by supplier.
3. Confirm payment list
Present the list to the user for approval. They may want to exclude certain bills or adjust amounts.
4. Process payments
For each approved bill:
clio bills pay "<billResourceId>" \
--amount <amount> \
--account "DBS Current" \
--date "2025-02-15" \
--method BANK_TRANSFER \
--json
5. Summary
Report: total bills paid, total amount, by supplier.
Key Rules
--due-beforefilters bills with due date on or before the specified date- Payment method defaults to
BANK_TRANSFER - For FX bills, use
--transaction-amountfor the bill currency amount - Always confirm the payment list with the user before executing
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 · 56 lines · 20 tokens per session scan A 5707e090e99d
jaz-payment-run is a command published in the GitHub repository teamtinvio/jaz-ai (7 stars, last pushed yesterday), licensed MIT. It adds 20 tokens to every session and 323 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
setup
An interactive setup wizard for configuring a Japanese tax accountant's office. It asks about the firm, clients, accounting software, expense rules, overseas services, invoices, payroll, and report sharing.
classify
A command that classifies one Japanese business transaction into an accounting category and tax type. It checks exclusions, past corrections, known keywords, and uses AI when needed.
correct
A command for correcting an incorrectly classified accounting transaction and saving the correction for future matching transactions.
import
A command that imports CSV files exported by Japanese accounting software and automatically classifies their transactions. CSV is a plain-text table format commonly used to move data between programs.
nightly
A command that runs overnight bookkeeping processing for every company connected through the freee accounting service.
report
A command that creates a monthly closing report for a client company. Monthly closing is the accounting process of summarizing and reviewing a month's transactions.