@agentoom/pi-spending-guard

This Skill addresses the pain point of uncontrolled LLM API costs. In practical development, developers often need to frequently call large models to complete multi-turn tasks or batch inference, but struggle to monitor the cost of each call in real-time, leading to budget overruns and end-of-month billing surprises. Pi-Spending-Guard allows you to precisely track each AI expense during task execution and set a configurable threshold. When the cumulative cost reaches this value, the task is automatically paused, preventing costs from ballooning indefinitely.

Usage is straightforward: simply install the extension first, then manage spending via natural language instructions or commands. For example, type /spending to view current spending and the limit, and /spending limit 5 to set the threshold to $5. When the actual spending reaches the limit, the system displays a dialog with four options: Continue (double the limit or reset the counter), Optimize prompt, or Stop the task. Simultaneously, the status bar shows a real-time spending progress bar like 💵 $1.23 / $3.00, keeping you informed of costs at all times.

It is ideal for teams or individuals who need fine-grained control over LLM call costs, especially users already leveraging pi.dev as an AI assistant platform for frequent multi-turn conversations or batch task processing, such as project managers, full-stack developers, and agent developers. For enterprises needing to manage AI budgets across multiple users or projects, hierarchical control can be achieved through global and project-level configuration files, preventing a single project from exhausting the overall budget.

It is recommended to configure a global default limit (default $3) uniformly at project startup and adjust the threshold based on the actual business complexity and call frequency. Note that it currently only supports the pi.dev platform and cannot be directly used with other LLM calling frameworks (e.g., direct OpenAI API calls). Additionally, if you choose "Continue (reset counter)" after a pause, the cumulative spending will be cleared, so pay attention to the continuity of budget tracking.