← Back to list

dsh-token-usage

DeepSeek Harness Other Low risk

Local-first four-bucket Token observability: persistent session/provider/model/day dashboards, trends, budget and anomaly signals, public-rate estimates, safe aggregate exports, and explicit opt-in usage or session-trajectory analysis.

本地优先的四 bucket Token 可观测性:持久会话/provider/model/日期仪表盘、趋势、预算与异常信号、公开费率估算、安全聚合导出,以及显式触发的用量/会话轨迹分析。

How to install

DeepSeek Harness dsh plugin add dsh-token-usage

About

dsh-token-usage 持久统计四类 provider Token bucket,提供趋势、预算、公开费率估算、聚合导出,并通过模型目录当前选中的已接入路由按需生成用量和会话轨迹报告。 截图采集自当前 DSH 界面;采集前已将用量、日期、路由与报告内容替换为明确标注的示例数据,不对应真实会话、模型配置或账单。 🗺️ 功能全景 | 领域 | 已实现能力 | | --- | --- | | **精确记账** | 分别记录未缓存输入、输出、缓存读取与缓存写入;reasoningTokens 已包含在输出中,不重复计算。流式 usage 先作为临时值,最终消息在同一 attempt 内覆盖它;重试与上下文压缩独立计数。 | | **多维聚合** | 以 provider / model、会话与 UTC 日期聚合普通对话、每次重试和上下文压缩;旧用量无法归因时单独披露,不破坏总量守恒。 | | **概览与活跃度** | 八项概览指标覆盖总量、输入、输出、缓存结构、公开费用、缓存读取避免费用、费率覆盖和有用量会话;30 周热力图支持四类 bucket 悬停与按日会话下钻。 | | **趋势与数据质量** | 支持 7/30/90 日环比、活跃天数和峰值日;运行率、预算预测、异常检测与 AI 日趋势只在逐日 bucket 完整可靠时启用,避免旧版合成日期造成低估。 | | **预算与异…

Recommendation signals

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

Meta

License
MIT
Language
TypeScript
GitHub stars
12
mo. downloads
660
Last push
2026-09-12
Created
2026-08-14

Links

Basic safety check

Findings
None
Sources
curated:awesome-dsh-plugin.com, curated:awesome-dsh-plugin/awesome-dsh-plugin
Topics
deepseek-harness, dsh-plugin, token-usage

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 ↗