agentmoneyOurs
Use to track and cap what an agent run costs: meter token/compute spend, set budgets, and surface cost as a first-class signal so an autonomous agent doesn't quietly burn through its limit.
- Score
- Unranked
- Evidence
- No signals yet
- Last commit
- as last read from GitHub; most reads are from 2 Sep 2026 or later
- Listed
Install
No one-command install. Set it up from its source.
What it is
A CLI for agent cost observability. It meters compute and token spend for an agent run, tracks it against a budget, and exposes cost as an explicit signal, the financial-rails counterpart to performance metrics. It answers "how much is this agent spending, and are we within budget?"
When to use it
For any long-running or overnight agent where unbounded spend is a real risk, and when you want to ration a fixed budget across a period. The trigger is "watch the cost" or "stay under this budget."
How to install / invoke
Install globally and run it to meter a session or report spend against a budget. Feed its signal into a routing policy that downshifts models as the budget tightens.
Notes
Cost is an observability dimension, not an afterthought. Pairs with a model-routing policy (cheaper models as budget shrinks) and with payment rails (the agent earning to fund its own spend).
Related
stripe-agent-toolkit
Use as the payments rail when an agent should earn or spend money in code (create customers, prices, payment links, and usage-based billing): the infrastructure behind an agent that funds its own compute.
Not Indexed
- agentmoney-cost