Skip to content
loomster

Estimate cost

llms.txt lists every page for a coding agent.

Optional: hand this page to your coding agentThe steps work by hand too.
Show the prompt
Read https://intentius.io/loomster/guides/estimate-cost/ and run `npm run synth` then `npm run estimate-cost` for the tier the person names.
Report each component's estimate, or the skip notice and its reason.
Never run `chant approve` or `just grant`, never deploy to or delete from a real AWS account unless the person asked for that in this session, never register an identity provider in Loom, and never push or edit the `chant/lifecycle` branch.

Result

Section titled “Result”

A monthly estimate per component for a tier, written to dist/cost-estimates/.

Prerequisites

Section titled “Prerequisites”

Infracost installed and signed in (infracost auth login, or INFRACOST_CLI_AUTHENTICATION_TOKEN in CI). Without it every component prints a skip notice and the script exits 0, so it never fails a build.

Steps

Section titled “Steps”

  1. Synthesize the tier you want priced:

    LOOM_TIER=production npm run synth

  2. Estimate:

    npm run estimate-cost

    It runs Infracost on each dist/*.template.json and prints what Infracost reports. chant carries no pricing data. An Infracost error, such as expired credentials or a CLI version that can’t read CloudFormation, is a skip with the reason.

  3. To get it weekly, turn on cost-report.yml with SCHEDULED_COST_REPORT=true and the token secret (Turn on scheduled Ops).

The estimate covers the infrastructure. Agent runtime, model tokens, AgentCore Memory and Evaluations are usage-based and outside it.

Next

Section titled “Next”

Cost for what drives cost on each tier.