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-supplier-recon)<a href="https://agentmods.dev/commands/teamtinvio/jaz-ai/jaz-supplier-recon"><img src="https://agentmods.dev/badge/commands/teamtinvio/jaz-ai/jaz-supplier-recon/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-supplier-recon"><img src="https://agentmods.dev/badge/commands/teamtinvio/jaz-ai/jaz-supplier-recon.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.00019 | $0.00406 |
| Opus 5.5 | $0.00008 | $0.00162 |
| Sonnet 5.5 | $0.00004 | $0.00081 |
| Haiku 4.5 | $0.00002 | $0.00041 |
Grade A, and why
jaz-supplier-recon 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 22d 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
Supplier Statement Reconciliation
Run the supplier recon playbook from the jaz-jobs skill (references/supplier-recon.md). Compares your AP ledger to the supplier's statement.
Usage
/jaz-supplier-recon "Acme Supplies" 2025-01
/jaz-supplier-recon all suppliers Q1
Workflow
1. Open the playbook
The steps are in the jaz-jobs skill: references/supplier-recon.md. Read it first and walk its steps in order; it names the exact tool or command for each one.
2. Pull AP data for the supplier
clio bills search --contact-name "Acme Supplies" --from 2025-01-01 --to 2025-01-31 --json
3. Compare against supplier statement
The user provides the supplier statement (PDF, email, or manually entered). Compare:
- Bills in Jaz vs items on supplier statement
- Amounts match vs discrepancies
- Items on statement not in Jaz (missing bills)
- Items in Jaz not on statement (timing differences or errors)
4. Resolve differences
- Missing bills: Create via
/jaz-bill - Amount discrepancies: Check tax, currency, credit notes
- Timing differences: Note for next period reconciliation
5. Generate aged AP for verification
clio reports generate aged-payables --to 2025-01-31 --json
Key Rules
--contact-namefilters bills by supplier name- Supplier statements are external documents; user must provide them
- Common discrepancies: missing credit notes, FX rate differences, GST/tax differences
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.
- 22d ago Changed 16836b0650ce
- 25d ago Changed · -2 lines 25223d7404f3
- 1mo ago Changed 3dd7025d1c88
- 1mo ago First seen · 56 lines · 19 tokens per session scan A 852232e7366c
jaz-supplier-recon is a command published in the GitHub repository teamtinvio/jaz-ai (8 stars, last pushed 9d ago), licensed MIT. It adds 19 tokens to every session and 406 once invoked, about $0.0001 per session on Opus 5.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.
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.
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.
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.