← Back to list

dsh-token-monitor

DeepSeek Harness Other Low risk

Header quota badge plus a usage-monitoring tab: live balance/quota remaining and reset countdown per provider, with requests, tokens (input/output/cache-read/cache-write), cache hit rate, estimated cost and average latency tracked per session, provider, model and client, stored locally in SQLite with cross-device import/export.

会话头部余量徽标 + 用量监控页签:实时展示各供应商余额/额度余量与重置倒计时,按会话/供应商/模型/客户端统计请求量、Token(输入/输出/缓存读/缓存写)、缓存命中率、预估费用与平均时延,本地 SQLite 留存历史,支持跨设备导入导出。

How to install

DeepSeek Harness dsh plugin add dsh-token-monitor

About

dsh-token-monitor DeepSeek Harness(DSH)Web 界面的大模型**余量与用量监控**插件:会话头部实时余量徽标 + 主区"用量"页签,本地 SQLite 记录每次调用的 token 与费用。 功能 · 安装 · 供应商适配 · 常见问题 · 架构 · 开发 [!NOTE] 需要 **Node.js ≥ 22**(依赖内置 node:sqlite)。仅支持 DSH Web 端(platform: web)。 功能 | 能力 | 说明 | | --- | --- | | 余量徽标 | 会话头部显示当前模型供应商余量(k3 · 5h 剩 82%),点击弹详情层 | | 用量页签 | 与"对话 / 轨迹"并列:token 用量、估算费用、趋势、排行、请求明细 | | 自动采集 | 字节级增量采集 DSH 会话日志(zstd 分帧),后台定时 + 手动触发 | | 历史导入 | 可导入 cc-switch 历史记录,重复导入不产生重复数据 | | 跨设备同步 | DSH 用量支持导出/导入 JSON 快照(明细 + 聚合),不同设备记录合并到一台设备,幂等不重复 | | 语言跟随 | 界面文案跟随 DSH 中文 / 英文切换 | 安装 从 npm(推荐) sh dsh plugin --profile web add dsh-token-monitor 从…

Recommendation signals

56 Tool quality · Based on stars, downloads, maintenance, security and docs
– User interest · Adjusted by in-site views, install copies and download clicks
56 Overall
0views
0unique visitors
0install copies
0download clicks
0outbound clicks

Meta

License
MIT
Language
JavaScript
GitHub stars
8
mo. downloads
2.3K
Last push
2026-09-24
Created
2026-08-18

Links

Basic safety check

Findings
None
Sources
curated:awesome-dsh-plugin.com, curated:awesome-dsh-plugin/awesome-dsh-plugin
Topics
deepseek, deepseek-ai, dsh, dsh-plugin, dsh-plugin-market, dsh-token-monitor, token-monitor

Related plugins

DeepSeek Harness
Score73

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.

☆ 202 ↓ 1.4K Other ↗
DeepSeek Harness
Score71

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.

☆ 1.5K ↓ 79.7K Other ↗
DeepSeek Harness
Score69

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.

☆ 9 ↓ 3.3K Other ↗
DeepSeek Harness
Score68

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.

☆ 8 ↓ 2.8K Other ↗