paolomandica/dsh-cost-usage-monitor
Account balance and session usage cost in the DeepSeek Harness composer dock.
dsh-cost-usage-monitor puts account balance and session usage cost in the DeepSeek Harness composer dock, next to the built-in stats pills. Billed tokens come from the tokenUsage session projection (provider-reported uncached input, cache read/write and output tokens), the priced route from the modelSelection projection, and the balance from DeepSeek's documented GET /user/balance endpoint, fetched host-side; the price per 1M tokens is editable and persisted locally.
Install
dsh plugin --profile desktop add dsh-cost-usage-monitorCopied verbatim from the README's install section (desktop profile). The README also gives a GitHub install and a local-path install.
Compatibility
The README describes a Host half and a browser half; the balance is fetched host-side because the API key belongs to the Host and api.deepseek.com serves no CORS headers. No specific Node or DSH version range is stated.
Details
- Repo: paolomandica/dsh-cost-usage-monitor
- Category: Usage & Billing
- Stars: 0
- Version: GitHub repo paolomandica/dsh-cost-usage-monitor; npm package dsh-cost-usage-monitor at 1.0.2 (registry check 2026-10-06).
FAQ
- Where does the balance come from?
- The README says the plugin's Host half resolves the DEEPSEEK_API_KEY credential and serves the balance from DeepSeek's documented GET /user/balance endpoint, which the browser half reads.
- Why is the balance fetched host-side?
- Because the API key belongs to the Host and api.deepseek.com serves no CORS headers, per the README.
Alternatives
YZz-S/dsh-token-cost-meter · LemCAE/dsh-balance · FengHuoLinShan/dsh-plugin-llm-balance