DSH HUB
HomePlugin StorePlugin PacksCommunityRankingsResourcesPublish Guide
Plugin source
Back to catalog

zhangqi423820-ai /

zhangqi423820-ai/dsh-spend-badge

Verified

Per-turn and per-session spend for DeepSeek Harness, appended inline to the usage row and the composer status bar.

★ 0 Stars0 Forks0 IssuesN/A Community rating0 Confirmed installs
View on GitHub
READMESource: main@79170ea8

dsh-spend-badge

Shows what a reply cost, inline in the DeepSeek Harness chat.

Where Looks like Meaning
End of each assistant reply's usage row 用量 45.6K tok · ¥0.036 cost of that turn, including every tool call inside it
Composer status bar under the input box 45.6K tok · 缓存命中 23% · ¥0.87 cost of the whole session so far

The amount is appended to the existing usage pill, so it inherits that pill's font size, colour and tooltip; nothing new is drawn on the page. Hovering the pill opens the usage details panel as before.

Per-turn amount on the usage row

Session total on the composer status bar

Prices are DeepSeek's published peak / off-peak rates, converted at the same numbers the provider charges.

Pricing model

CNY per million tokens, [off-peak, peak]:

Model Cache hit Cache miss Output
deepseek-flash, deepseek-v4-flash 0.02 / 0.04 1 / 2 4 / 8
deepseek-v4-pro 0.15 / 0.3 4.5 / 9.0 13.5 / 27.0
  • Peak: Monday to Friday, 09:00–12:00 and 14:00–18:00 Beijing time.
  • Off-peak: every other hour, plus weekends and public holidays from 2026-08-23 onward.
  • One step costs hit_tokens × hit_price + miss_tokens × miss_price + output_tokens × output_price. Reasoning tokens are already inside output tokens and are not charged twice.
  • Models not in the table fall back to the flash rate.

Where the numbers come from

Two sources, same events:

  1. Live — the plugin subscribes to the host's session/event stream and accumulates assistant/message usage by (session, turn). This only covers calls made after the plugin loaded.
  2. Session log — ~/.dsh/sessions/<cwd>/session-<id>/session.v4.jsonl.zstd is replayed to recover the whole history, including turns from before the plugin was installed. The file is a sequence of concatenated zstd frames; Node's zstdDecompressSync stops after the first frame, so the reader splits on the 28 B5 2F FD magic and decodes each frame separately.

For each turn the larger of the two values wins: the log is the authoritative ledger but may lag behind the newest step, while the live counter only ever holds a fragment that started at zero.

HTTP surface

Both routes are read-only and served from the harness's own origin:

  • GET /dsh-spend/client.js — the page script
  • GET /dsh-spend/data?session=<id> — { ok, sessionId, turns: { turn: cny }, total, peak, file, debug }

Requests carrying a foreign Origin (or a cross-site fetch) are rejected.

DOM anchors

The page script locates two elements and appends a text node; it re-applies itself through a MutationObserver with a 120 ms debounce plus a 3 s poll, so re-renders and conversation switches are picked up.

  • [data-turn-tail] — one per turn, the attribute value is the turn number
  • [data-composer-stat="usage"] — the composer usage stat

Install

From the market, or directly from this repository:

dsh plugin add github:zhangqi423820-ai/dsh-spend-badge

Then restart DSH once. The client script itself is re-read on every request, so edits to assets/spend-meter.js only need a page refresh.

Uninstall

Remove the bundle from the profile (dsh.profile.bundles, or enabled: false) and restart DSH.

A restart is required for host-side changes: the harness does not watch plugin source, and a route registered through ctx.webServer.register() outlives the plugin instance that registered it if teardown is not wired up — this plugin registers its disposal through ctx.effect() for that reason.

Troubleshooting

debug in the data route reports what each half saw:

  • logBytes / logTurns — log size, turns decoded
  • liveTurns — turns held by the live counter
  • cache — whether the log parse was served from cache (key: mtime + size)
  • logError — decode failure, if any

logTurns: 0 with a non-null logError means the log could not be decoded; liveTurns: 0 means no session/event reached the plugin.

Compatibility

Written against DeepSeek Harness 0.2.2-rc.1. It relies on the session/event event payload (data.turn, data.usage, data.message.source.model), the webserver/index-inject hook, and the session.v4.jsonl.zstd log format.

License

MIT

—/ 5

No ratings yet

Verified DSH bundle

Commit 79170ea84f92

Community comments

No comments yet. Be the first to write one.

DSH HUB

A community index for DSH plugins. Not an official GitHub or DeepSeek AI product.

CommunityResourcesAPIAbout