Offline, read-only estimation from an exported JSON document. No provider prices are fetched, and token counts are supplied rather than inferred. The report calls computed costs estimatedUsd; optional historical spend stays in measuredSpendUsd. A baseline comparison is labelled projectedSavingsUsd, never achieved savings.
This walkthrough uses the tool's public README and checked-in example files. Run the command from a repository checkout with Node.js 22+; inspect the source before using it on your own files.
Run the checked-in example
node bin/automation-cost-estimator.mjs --root examples --input passing.json
node bin/automation-cost-estimator.mjs --root examples --input incomplete.json --human
npm run checkRead the result
--root names the evidence directory. --input is relative to it. The optional --out report.json writes the same JSON report inside the root after checking the destination. JSON always goes to stdout; --human adds a short summary on stderr. --help lists options. No option makes a network request or changes the input. A bad option/configuration gives exit 2 with empty stdout. An unreadable, non-UTF-8, malformed or unsupported input gives an incomplete JSON report and exit 2.
Where this check stops
This local walkthrough does not establish the state of a live production system or replace the limits documented in the repository.
Before adapting the command to your own workflow, review the accepted inputs, exit codes and safety boundaries in the README.
Compiled with AI assistance from checked-in public documentation and example scripts. Run the example and review the repository's current documentation before relying on its result.