← Back to list

dsh-session-cost

DeepSeek Harness Other Low risk

Composer cost chip: prices the current session DeepSeek API spend message-by-message with the official pricing table (incl. the 2026-08-17 peak/off-peak policy); hover for the breakdown, today (DSH) total and account balance. DeepSeek models only.

输入框右侧会话成本芯片:按官方价表(含 2026-08-17 峰谷价)逐消息计价当前会话的 DeepSeek API 花费,悬停查看计价明细、今日(DSH) 消耗与账户余额;仅 DeepSeek 模型计价,其他模型不计价不显示。

How to install

DeepSeek Harness dsh plugin add @phynez_1103/dsh-session-cost

About

English | 中文 dsh-session-cost DeepSeek Harness(dsh)Web 界面的**会话花费插件**:把当前会话的 DeepSeek API 累计花费显示为输入框旁的一个小徽标。 特性 **输入框实时花费**:在 conversation.input.right 槽位(模型选择器左侧)显示当前会话的 DeepSeek API 花费(¥),每 5 秒刷新。 **严格模型门槛**:**仅当会话当前模型为 DeepSeek 时生效**;使用其他模型(MiniMax、Kimi 等)时徽标自动隐藏,且**非 DeepSeek 模型的请求完全不计价、不进入统计**。 **悬停浮窗**:弹出与项目风格一致的浮窗,展示: 会话花费明细**表格**:输入(未命中) / 缓存命中 / 输出 × 数量 × 有效单价 = 金额; 今日(DSH) 用量:本机 DSH 会话今日(北京时间)消耗的 DeepSeek 花费; 账户余额:读 DSH 凭证中的 DEEPSEEK_API_KEY,经 DeepSeek 官方 user/balance 接口获取。 **官方计价引擎**:按 DeepSeek 官方价格时间表对**每条** assistant/message 消息**按其发生时刻**逐条计价,自动应用 2026-08-17 起的高峰/空闲定价(北京时间 09:00–12:0…

Recommendation signals

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

Meta

License
MIT
Language
JavaScript
GitHub stars
0
mo. downloads
158
Last push
2026-08-20
Created
2026-08-16

Links

Basic safety check

Findings
None
Sources
curated:awesome-dsh-plugin.com, curated:awesome-dsh-plugin/awesome-dsh-plugin
Topics
dsh-plugin, dsh-plugin-desktop, dsh-plugin-market, dsh-plugins

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 ↗