← Back to list

dsh-llm-cost

DeepSeek Harness Other Low risk

Per-turn and session-wide LLM cost metering: a dollar cost line under each message, a session cumulative total with hover breakdown, and an LLM+web price auto-refresh tool.

按轮次与会话统计 LLM 成本:每条消息下方显示美元成本、会话累计总额(悬停看分项),以及 LLM+联网的价格自动刷新工具。

How to install

DeepSeek Harness dsh plugin add github:chenyinrusi/dsh-llm-cost

About

dsh-llm-cost 让 DeepSeek Harness 显示**每个 turn、每个 step 的 LLM 成本**(美元),并在价格过期时用 LLM + 联网自动更新价格表。 DSH 已经精确记录了每个 step 的真实 token 用量(assistant/message 的 usage:输入/输出/缓存读/缓存写),但**没有任何美元成本概念**。dsh-llm-cost 补上缺失的那一环:把「用量 × 单价」变成 DSH 的持久事实(costUsage session projection),并在每个对话框下方的 stats 行里渲染出该 turn 的成本。 工作原理 **host 端(node)**:一个 session projection 单元(照 token-meter 的骨架),在 session/event 上折叠: request/context(解析后的 provider/model 路由,post-fallback)决定每个 step 用的模型; assistant/message(或 assistant/chunk 的 usage chunk)报告该 step 的用量; 单价表 → costUsd,同一 turn/step 的重复采样做**替换**而非重复累计。 **client 端(浏览器)**:注册到 conversation.chat.tu…

Recommendation signals

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

Meta

License
MIT
Language
TypeScript
GitHub stars
1
mo. downloads
–
Last push
2026-08-24
Created
2026-08-16

Links

GitHub ↗ Report issue ↗

Basic safety check

Findings
curated 收录但无 npm 包/安装命令
Sources
curated:awesome-dsh-plugin.com, curated:awesome-dsh-plugin/awesome-dsh-plugin
Topics
deepseek-harness, dsh, dsh-plugin, llm-cost

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 ↗