terseai
Uncontrolled token spend in multi-agent AI coding workflows creates unpredictable cloud costs and potential budget overruns.
Claude Code & Cursor token usage monitor and cost tracker for macOS & Windows. Live token/cost/burn monitoring across 8 AI coding agents, a budget circuit breaker that stops runaway agents before the next API call, an MCP manager, and 40-70% on-device prompt compression.
- Monitor real-time token consumption and costs across multiple AI coding agents simultaneously.
- Stop runaway AI agents before they make expensive API calls using budget circuit breaker.
- Compress prompts by 40-70% on-device to reduce token usage and lower API costs.
Uncontrolled token spend in multi-agent AI coding workflows creates unpredictable cloud costs and potential budget overruns. Circuit-breaker controls and real-time monitoring prevent wasteful API calls before they occur, while on-device compression reduces token consumption by 40–70% without sacrificing quality.
Engineering teams and DevOps leaders managing multiple AI coding agents who need cost visibility and automated spending guardrails.
https://github.com/Terse-AI/terseai
By Terse-AI
How to Get It
claude plugins install Terse-AI/terseai
Tip: Paste this into a Claude Code conversation. Verify command matches your Claude Code version.
Auto-generated from the tool's public listing — not hands-on verified. Cross-check against the source repo's README before running.
After installing, paste this into Claude:
Help me monitor real-time token consumption and costs across multiple AI coding agents simultaneously
Trust Signals Auto-scanned
Community Pulse Growing
Discussed on Hacker News
- Show HN: Terse, TypeScript First Workflow Builder — Hacker News · 3 pts
1 mentions across 1 sources
Reviewer notes
Auto-scanned review. These are observations, not a security certification.
Scored from trust signals (evidence-eval-v1): 33 GitHub stars; contributors unknown; last commit 0d ago; license MIT.
Things to check
- Scanned, not hands-on tested — this entry was auto-scanned from public metadata (GitHub metrics, license, security flags). No reviewer has run it, and no tool-specific limitations have been documented yet.
How to evaluate tools before deploying →
Data shown here comes from public APIs and automated scanning. Reviewer notes reflect one person's experience. This is not a security certification or legal recommendation. Always evaluate tools according to your own organization's policies.
Evaluation
Scored from trust signals (evidence-eval-v1): 33 GitHub stars; contributors unknown; last commit 0d ago; license MIT.