DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to set a spending budget and get warned before you go over with DSH Cost Meter

Track budget used percentage and today's share of budget, with warnings at 80 percent and over-budget at 100 percent.

  • Money
  • Beginner
  • 15 minutes
  • From the README
  • Any agent

Who it is forA developer or team lead who has a fixed monthly or daily amount for model usage and needs an early warning.

The problemSpending drifts past a set amount when no one checks running totals against the limit.

The outcomeThe budget box in the sidebar shows used percentage, a progress bar, and how much of the limit is used, and the quota strip shows the budget chip.

What you need first

  • DeepSeek Harness (DSH) version 0.2.0 or later installed
  • The dsh-cost-meter plugin installed from the README Installation section
  • Provider keys or accounts only for the balance and quota sources you want to query

Steps

  1. Open Settings → Cost and enter your budget amount.
  2. Check the budget box between the balance row and the settings button in the sidebar.
  3. Watch for the warning state at 80 percent and the over-budget state at 100 percent.
  4. Turn on the quota strip to see budget used percentage above the input box.

Prompt for your agent

Using the dsh-cost-meter plugin in DeepSeek Harness 0.2.0 or later, read the current budget used percentage and today's cost against the budget limit, and say whether the warning or over-budget state applies. Verify that the figure matches the budget box in the sidebar.

Caveat. The README describes the budget as a user-set limit and does not say whether it can cap spending automatically, so it only reports usage.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page