dsh-plugin-usage-meter
Local-first usage and cost meter for the DSH web UI: composer button with live session cost and balance; panel with a stacked per-model daily/7-day chart priced per effective list-price interval (official pricing page synced daily), monthly usage tiers with a canvas share card, 30/50/85% context-pressure warnings with one-click /compact, budget alerts, and an in-panel npm update check with one-click update.
本地优先的用量与费用仪表：输入框下方按钮显示实时费用与余额，面板含按模型堆叠的当日/近 7 天柱状图（按刊例价生效区间计价、官方定价页每日同步）、本月消耗段位与画布分享卡片、30/50/85% 上下文压力三档预警与一键 /compact、预算提醒，以及面板内 npm 检查更新与一键更新。
How to install
dsh plugin add dsh-plugin-usage-meter About
dsh-plugin-usage-meter 是什么 · 功能特性 · 界面预览 · 快速开始 · 设置 · 定价说明 · 数据与隐私 · 常见问题 · 已知限制 是什么 一个纯社区维护的 DeepSeek Harness（dsh）网页插件：在输入框下方放一个**按钮样式的用量条**，实时显示当前会话的 token 用量与按 DeepSeek 官方刊例价（峰谷 × 双币种）估算的费用；点开面板能看到当日/近 7 天**按模型堆叠的柱状图**、模型分布、上下文占用、账户余额与预算进度，并把跨会话用量持久化成本地账本。 | 能力 | 原生 dsh web | 装本插件后 | | --- | --- | --- | | 会话 token / 费用 | 内置 token 统计（无费用） | 实时估算费用 + 今日累计，按钮化可展开 | | 峰谷计价 | 无 | 高峰/空闲双时段，CNY/USD 双币种 | | 用量可视化 | 无 | 当日小时级 / 近 7 天按模型堆叠柱状图 | | 模型费用分布 | 无 | 事件级归属，跨会话累计 | | 账户余额 | 无 | 官方余额接口 + 60s 缓存 + 手动刷新 | | 预算提醒 | 无 | 每日预算进度条，≥80% 黄、超支红 | | 跨会话账本 | 无 | 按天×模型、当日按小时×模型，原子持久化 …
Recommendation signals
Meta
- License
- MIT
- Language
- JavaScript
- GitHub stars
- 4
- mo. downloads
- 3.4K
- Last push
- 2026-09-17
- Created
- 2026-08-19
Basic safety check
- Findings
- None
- Sources
- curated:awesome-dsh-plugin.com, curated:awesome-dsh-plugin/awesome-dsh-plugin, curated:0xsline/awesome-deepseek-harness
- Topics
- balance, billing, cost, deepseek-harness, dsh, dsh-plugin, usage, usage-meter
Related plugins
TokenLedger
zh667/TokenLedger
Sidebar usage panel that attributes tokens to the relay site that served each request, read from your existing provider config: today/month/all-time totals, per-site and per-model breakdowns, a year activity heatmap, and New API / Sub2API / DeepSeek balances.
dsh-context
bowenliang123/dsh-context
DSH context insight panel: Context dashboard + /context command + Context browser — one-stop context lifecycle management with categorized composition, content details, evolution trends, compaction/injection events, and stats.
dsh-usage-statistics-panel
HaoyueQin/dsh-usage-statistics-panel
Usage statistics settings panel: 26-week activity heatmap, daily token trend with a cache hit-rate curve, per-model donut and breakdown, time-range filters, summary cards, one-time historical backfill and lossless rebuild.
dsh-all-usage
ParticleLight/dsh-all-usage
Analyze usage across models, providers, workspaces, and time ranges — including custom start/end dates over the full retained history — with live cache-hit visibility and separate model and provider breakdowns. Includes hourly single-day trends, daily cross-day trends, a 53-week GitHub-style heatmap, usage streaks, model and workspace Token-share donut charts with Token, cost, and percentage details, independent combinable filters, cache-efficiency trends, DeepSeek account balance, workspace aliases, CSV export, and a durable ledger that preserves successfully flushed usage after session deletion — and after a workspace is deleted, where its recorded usage is summed into one Deleted row — and rebuilds incrementally — on restart, unchanged sessions are applied from the ledger without re-reading their logs (a per-session log revision is the change signal), and only changed/new events are folded. The workspace registry is kept fresh automatically through the DSH domain/changed probe: only added/removed workspaces are reprocessed incrementally, unchanged workspaces reuse their computed aggregates and ledger with zero rescan, and usage is strictly limited to DSH-registered workspaces (unregistered cwds are ignored). After a scan, lightweight revision status fetches full history only when the Host/data state changes and exposes non-sensitive sync health (revision reuse, rereads, ledger recovery, and failures). Token accounting is explicit: input is fresh (cache read/write and reasoning are separate buckets) and zero-usage replays never overwrite recorded usage. Chinese uses local time, English uses UTC; API access is loopback-only.