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-fa-review)<a href="https://agentmods.dev/commands/teamtinvio/jaz-ai/jaz-fa-review"><img src="https://agentmods.dev/badge/commands/teamtinvio/jaz-ai/jaz-fa-review/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-fa-review"><img src="https://agentmods.dev/badge/commands/teamtinvio/jaz-ai/jaz-fa-review.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.00018 | $0.00439 |
| Opus 5 | $0.00009 | $0.00219 |
| Sonnet 5 | $0.00004 | $0.00088 |
| Haiku 4.5 | $0.00002 | $0.00044 |
Grade A, and why
jaz-fa-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 11d 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
Fixed Asset Review
Execute the FA review workflow via clio jobs fa-review. Reviews the fixed asset register for accuracy and completeness.
Usage
/jaz-fa-review
/jaz-fa-review check for assets to dispose
Workflow
1. Generate the blueprint
clio jobs fa-review --json
2. Review assets
The blueprint walks through:
- Assets with zero remaining book value (candidates for write-off/disposal)
- Assets past useful life but still active
- Depreciation accuracy vs policy
- Missing or misclassified assets
3. Process disposals
For assets to dispose, use the calculator first:
clio calc asset-disposal --cost 50000 --salvage 5000 --life 5 --acquired 2020-01-01 --disposed 2025-06-15 --proceeds 8000 --json
Then execute the disposal recipe:
clio ct asset-disposal --cost 50000 --salvage 5000 --life 5 --acquired 2020-01-01 --disposed 2025-06-15 --proceeds 8000 --start-date 2025-06-15 --json
4. Verify
Check the trial balance for fixed asset and accumulated depreciation accounts:
clio accounts search --ref "Fixed Asset" --json
clio reports generate trial-balance --to 2025-12-31 --json
Key Rules
- Disposals compute gain/loss: proceeds - (cost - accumulated depreciation)
- The asset-disposal recipe creates the disposal journal + notes for FA deregistration
- FA deregistration in Jaz's native FA module is a manual step (not API-accessible yet)
- Depreciation methods for CLI calculators:
sl(straight-line),ddb(double declining),150db
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.
- 11d ago First seen · 62 lines · 18 tokens per session scan A 91fe2e336e6d
jaz-fa-review is a command published in the GitHub repository teamtinvio/jaz-ai (7 stars, last pushed yesterday), licensed MIT. It adds 18 tokens to every session and 439 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.