AI Agent Hub
Back to plugins
🖥️

dsh-usage-guard

Client Updated 2026.08.25

Run the following command in DeepSeek Harness:

dsh plugin install hb-degithub/dsh-usage-guard

Paste the following prompt into your AI chat to install this plugin:

In DeepSeek Harness, run dsh plugin install hb-degithub/dsh-usage-guard to install this plugin. Source: https://github.com/hb-degithub/dsh-usage-guard

About this plugin

When you work with the DeepSeek Harness Web GUI, token consumption and API costs tend to scatter across individual sessions, making them hard to quantify and easy to overlook until the bill arrives. dsh-usage-guard plugs exactly that gap: it silently hooks every assistant message in the background, folds usage into daily buckets keyed by provider and model, survives restarts, and even backfills from historical session logs on first run—no manual bookkeeping required.

Open Settings → Usage to see a full dashboard: six stat cards summarizing tokens, sessions, messages, active days, current streak, and top model; a GitHub-style yearly activity heatmap with weekday and month labels plus a hover detail card for each day; a multi-series trend chart that plots input, output, cache-hit, cache-write, and cost on dual axes with a 7-day / 30-day toggle; and a donut chart breaking down usage by model. The cost-estimation module ships with DeepSeek list prices and lets you set custom per-million-token rates for input, output, cache-read, and cache-write. Models without a configured price are simply excluded from cost tallies rather than guessed at. If you want a hard guardrail, the daily-limit guard offers two modes: warn shows a global banner, while block aborts over-limit LLM requests before they ever hit the network.

It is well suited to individual developers who want usage visibility without changing their workflow, and to teams that call multiple models or providers and need per-model cost accounting. The plugin is bilingual (zh/en), follows DSH theme tokens, and has zero external runtime dependencies—install and go.

Use Cases

  • Track daily token usage and API spend at a glance
  • Break down costs across multiple models and providers
  • Set daily caps and block over-limit requests before they hit the network

Best For

  • Individual developers using the DSH Web GUI daily
  • Teams calling multiple models that need per-model cost accounting
  • Engineers who want usage visibility without changing their workflow