Appends what each turn cost to its usage row and the running session total to the composer status bar, priced on DeepSeek's published peak and off-peak rates. Its HTTP routes have no DSH access check, so a web page open in your browser could call them.
Install
# from GitHub (first run asks for allowBuilds approval — follow the hint, retry)
dsh plugin --profile web add github:zhangqi423820-ai/dsh-spend-badge
Any plugin you install runs third-party code with your own permissions — it can read your files, use your credentials, and reach the network, and tool approvals don’t sandbox it. GitHub-sourced plugins also run build scripts at install time — pnpm blocks those until you allow them, so an install can stop with ERR_PNPM_GIT_DEP_PREPARE_NOT_ALLOWED or ERR_PNPM_IGNORED_BUILDS; dsh prints the exact key to add under allowBuilds in your profile’s pnpm-workspace.yaml, and the install works on the next run. Allowing a build is a trust decision: only install sources you trust, and pin a commit (github:owner/repo#sha).
README
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.


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:
- Live — the plugin subscribes to the host's
session/eventstream and accumulatesassistant/messageusage by(session, turn). This only covers calls made after the plugin loaded. - Session log —
~/.dsh/sessions/<cwd>/session-<id>/session.v4.jsonl.zstdis replayed to recover the whole history, including turns from before the plugin was installed. The file is a sequence of concatenated zstd frames; Node'szstdDecompressSyncstops after the first frame, so the reader splits on the28 B5 2F FDmagic 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 scriptGET /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 decodedliveTurns— turns held by the live countercache— 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
Links
More in this category
bowenliang123/dsh-context★ 5191
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.
Han-1413141/dsh-cost-meter★ 705
Per-session and daily API cost, budget with usage %, official balance, history dashboard, and one-click official price sync with peak/off-peak pricing.
wssfk12138/dsh-damage-pulse★ 290
Tracks DeepSeek token usage, per-call and session costs, and account balance with cache-aware charge animations in the DSH Web UI.
zh667/TokenLedger★ 205
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.
Ychris12138/dsh-usage-stats★ 190
Multi-provider usage dashboard with provider/model token breakdowns, calendar drill-downs, account balances, and OpenCode Go / Z.ai subscription quota tracking.
Mt-Youya/dsh-plugins#sessions-insight★ 166
Browse Claude Code, DSH and Codex session logs by working directory, with per-turn context composition, token usage, compaction markers and cost estimates.
Community comments
Comments are public GitHub Discussions. Loading them connects to GitHub and Giscus; a GitHub account is required to post.