AI Agent Hub
Back to plugins
🖥️

dsh-ui-cost-meter

Client Updated 2026.09.14

Run the following command in DeepSeek Harness:

dsh plugin install yuu1111/dsh-ui-cost-meter

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

Run dsh plugin install yuu1111/dsh-ui-cost-meter in your terminal to install the plugin; the source lives at https://github.com/yuu1111/dsh-ui-cost-meter . Once installed, the cost pill appears beside the composer right away.

About this plugin

When you drive long multi-turn sessions through DeepSeek Harness, token spend scatters across pagination, retries, cache hits and model switches. After the fact, reconciling how much a session cost and where the tokens went means digging through logs and squaring them against a bill. dsh-ui-cost-meter drops a persistent cost pill right beside the composer so the running total is always in view without leaving the GUI.

The number is folded from the harness own durable provider usage log via the session projection seam, so paging and compaction cannot alter it and a page reload does not reset it. Clicking the pill opens a breakdown panel styled identically to the shipped stats pills, itemising each priced route, every cache bucket, and the tokens left unpriced because no rate matched. A missing rate never silently zeroes out: the amount carries a trailing plus sign and the panel names exactly how many tokens were skipped.

All rates live on the plugin row, expressed per million tokens, keyed by route with an optional global fallback, and the currency symbol is whatever you type in. The host half registers the cost projection; the browser half renders a React portal into the existing composer stats row so the pill inherits the shell CSS variables, spacing and radius without editing cordis.patch.yml.

Built for developers and teams who hop between DeepSeek V4.1 Flash, V4 Pro and other routes and want a live, at-a-glance read on per-session spend. The figures are the harness token count times your configured rates, not a provider invoice, so the provider bill remains the source of truth.

Use Cases

  • Track cumulative token spend in real time during long multi-turn sessions without leaving the GUI
  • Decompose per-route cost when switching between Flash, Pro and other DeepSeek models in one session
  • Audit cache hits and explicitly flag unpriced tokens left unmatched by any rate entry
  • Verify that paging, compaction, and retries do not alter the accumulated session total

Best For

  • Developers who run long sessions in the DeepSeek Harness Web GUI and want at-a-glance cost awareness
  • Teams managing multi-route token budgets who need per-route cost breakdowns
  • Solopreneurs and OSS users who prefer in-GUI cost accounting over manual log-vs-invoice reconciliation