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-audit-prep)<a href="https://agentmods.dev/commands/teamtinvio/jaz-ai/jaz-audit-prep"><img src="https://agentmods.dev/badge/commands/teamtinvio/jaz-ai/jaz-audit-prep/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-audit-prep"><img src="https://agentmods.dev/badge/commands/teamtinvio/jaz-ai/jaz-audit-prep.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.00022 | $0.00456 |
| Opus 5 | $0.00011 | $0.00228 |
| Sonnet 5 | $0.00004 | $0.00091 |
| Haiku 4.5 | $0.00002 | $0.00046 |
Grade A, and why
jaz-audit-prep 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 9d 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
Audit Preparation
Execute the audit prep workflow via clio jobs audit-prep. Generates a comprehensive pack of reports and schedules.
Usage
/jaz-audit-prep 2025
/jaz-audit-prep 2024 for tax filing
Workflow
1. Generate the blueprint
clio jobs audit-prep --period 2025 --json
2. Generate core reports
# Trial Balance
clio reports generate trial-balance --to 2025-12-31 --json
# Balance Sheet
clio reports generate balance-sheet --to 2025-12-31 --json
# Profit & Loss
clio reports generate profit-loss --from 2025-01-01 --to 2025-12-31 --json
# Cash Flow Statement
clio reports generate cashflow --from 2025-01-01 --to 2025-12-31 --json
# Aged AR
clio reports generate aged-ar --to 2025-12-31 --json
# Aged AP
clio reports generate aged-ap --to 2025-12-31 --json
3. Supporting schedules
The blueprint identifies additional schedules needed:
- Fixed asset register and depreciation schedule
- Loan and lease schedules (from capsule transactions)
- Prepaid and accrual schedules
- Intercompany balances
- Bank reconciliation at year-end
4. Compile and present
Organize outputs for the auditor. Flag any items that need user confirmation or additional documentation.
Key Rules
- Report date fields vary: trial-balance uses
endDate, balance-sheet usesprimarySnapshotDate, P&L usesstartDate/endDate— the CLI handles this, just use--from/--to - Audit prep is typically for a full fiscal year
- Some schedules come from capsule transaction data — list capsules with
clio capsules list --json
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.
- 9d ago First seen · 65 lines · 22 tokens per session scan A d06d0000ae7f
jaz-audit-prep is a command published in the GitHub repository teamtinvio/jaz-ai (7 stars, last pushed yesterday), licensed MIT. It adds 22 tokens to every session and 456 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.