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-credit-control)<a href="https://agentmods.dev/commands/teamtinvio/jaz-ai/jaz-credit-control"><img src="https://agentmods.dev/badge/commands/teamtinvio/jaz-ai/jaz-credit-control/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-credit-control"><img src="https://agentmods.dev/badge/commands/teamtinvio/jaz-ai/jaz-credit-control.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.00021 | $0.00518 |
| Opus 5 | $0.00010 | $0.00259 |
| Sonnet 5 | $0.00004 | $0.00104 |
| Haiku 4.5 | $0.00002 | $0.00052 |
Grade A, and why
jaz-credit-control 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 12d 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
Credit Control
Execute the credit control workflow via clio jobs credit-control. Reviews AR aging and generates a chase list.
Usage
/jaz-credit-control overdue more than 30 days
/jaz-credit-control full AR review
Workflow
1. Generate the blueprint
clio jobs credit-control --overdue-days 30 --json
2. Review aged receivables
clio reports generate aged-ar --to 2025-02-28 --json
The blueprint breaks down receivables by aging bucket: current, 1-30, 31-60, 61-90, 91+.
3. Generate chase list
The blueprint produces a prioritized list of overdue customers with:
- Contact details
- Invoice references and amounts
- Days overdue
- Suggested action (reminder, follow-up, escalation)
4. Assess bad debts
For severely overdue amounts, consider ECL provisioning:
clio calc ecl --current <amt> --30d <amt> --60d <amt> --90d <amt> --120d <amt> --rates 0.5,1,3,10,50 --json
5. Record provisions (if needed)
Post the provision journal with the same buckets and rates:
clio ct ecl --current <amt> --30d <amt> --60d <amt> --90d <amt> --120d <amt> --rates 0.5,1,3,10,50 \
--existing-provision <amt> --start-date <YYYY-MM-DD> --plan --json
Review the plan output, then re-run without --plan to post. Entries are created as drafts unless you pass --finalize. Needs Bad Debt Expense and Allowance for Doubtful Debts accounts.
Key Rules
--overdue-dayssets the threshold for the chase list (default: 30)- AR aging report uses
aged-arreport type - ECL provisioning uses IFRS 9 simplified approach (5-bucket matrix)
- No
amountDuefield on invoices — checkpaymentRecordsto determine remaining balance
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.
- 12d ago First seen · 66 lines · 21 tokens per session scan A 702fc11aba9d
jaz-credit-control is a command published in the GitHub repository teamtinvio/jaz-ai (7 stars, last pushed today), licensed MIT. It adds 21 tokens to every session and 518 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
correct
A command for correcting an incorrectly classified accounting transaction and saving the correction for future matching transactions.
nightly
A command that runs overnight bookkeeping processing for every company connected through the freee accounting service.
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.
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.
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.