dsh-plugin-session-cost-pill
在 DeepSeek Harness 编写器停靠栏中实时显示会话支出，并根据每个助手步骤对应时间戳的 DeepSeek 高峰期或非高峰期费率计价。
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add dsh-plugin-session-cost-pill@1.1.2Plugin Session Cost Pill 以 dsh-plugin-session-cost-pill 发布，当前版本为 1.1.2。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
点击下方 Badge 复制 Markdown，粘贴到 README 即可。
验证 package.json 声明的 GitHub 仓库，即可管理这个公开页面。认领后，Hub 会优先安排当前版本的安全扫描，并在通过后公开展示结果。
认领这个 Plugin →Live session spend, right in the composer dock.
Session cost pill in the DeepSeek Harness composer dock
DeepSeek tells you how many tokens you burned. It does not tell you what that cost. This plugin does — live, per session, without a single line of patched harness source.
The composer dock already tracks turns, speed, tokens, and context. The cost pill joins that row:
| Pill | Shows |
|---|---|
| ⏱ activity | turns · steps · decode speed |
| 💾 usage | total tokens · cache-hit rate |
| 💸 cost | estimated spend for this session |
| 🪫 context | context-window pressure |
The glyph climbs with the session total, so the row reads at a glance before the number does:
| 💸 | 💵 | 💰 | 🔥 | 🚨 |
|---|---|---|---|---|
| under $1 | under $5 | under $20 | under $100 | $100 and up |
Click it and the breakdown opens: uncached input, cache reads, and output, each priced separately, plus how much of the total was charged at peak rates and how many steps that covered. It closes on Escape, on a click outside, or on a second click — the browser's own popover behaviour, so the plugin ships no dialog state, listeners, or positioning code of its own.
The cost pill The cost breakdown panel open above the pill
Full window with the pill running
dsh plugin --profile web add ~/code/github.com/vegerot/deepseek-harness-session-cost-pill
dsh plugin --profile desktop add ~/code/github.com/vegerot/deepseek-harness-session-cost-pill
That is the whole install. No build, no bundler, no dependencies. Restart the profile and refresh.
Most cost trackers multiply a session's tokens by one flat rate. That is wrong for DeepSeek twice over.
Prices double during peak hours, so a single rate per model cannot price a session.
| Model | Tier | Cache hit input | Cache miss input | Output |
|---|---|---|---|---|
deepseek-flash | off-peak | 0.003 | 0.15 | 0.60 |
deepseek-flash | peak | 0.006 | 0.30 | 1.20 |
deepseek-v4-pro | off-peak | 0.022 | 0.66 | 1.98 |
deepseek-v4-pro | peak | 0.044 | 1.32 | 3.96 |
USD per 1M tokens, transcribed from Models & Pricing.
Peak is 01:00–04:00 and 06:00–10:00 UTC, Monday–Friday. Everything else — all weekend — is off-peak.
So this plugin prices every assistant step at the rate in effect for that step's own timestamp. A session that crosses a peak boundary gets a correctly blended total instead of a guess.
A cache hit costs a fraction of a cache miss. A tracker that folds all prompt tokens into one bucket will miss the mark badly on a long agent session — exactly the kind that reads 96% cache-hit.
DeepSeek publishes no pricing API, but its Platform console reports authoritative cost. Checking this plugin's table
against one real account's October deepseek-flash usage:
tokens: hit 140.56512M miss 2.828971M out 0.758458M
published all-off-peak total = $1.301116
platform's own billed total = $0.453778 + ¥6.0056894
= $1.301116 at FX 7.0877 CNY/USD
A 0.11% match. The table is right, and that month's usage was effectively all off-peak — assuming peak would have doubled the estimate.
It is an ordinary Cordis client plugin. Nothing in the harness is patched, forked, or monkey-patched.
ctx.slots.inject('conversation.composer.dock', () => ctx.slots.register({
name: 'conversation.composer.dock',
id: 'cost-pill',
order: 2, // joins the activity (0) and usage (1) pills
}, CostPill));
The pill reads the chat snapshot through the session standard kit and folds it:
useChat → every settled assistant step, each carrying its own time and provider usageuseProjection('modelSelection') → the session's modeltotal = Σ over steps costOfUsage(step.usage, model, isPeak(step.time))
isPeak classifies one request from its UTC weekday and hour, so pricing is per-request rather than per-session.
Honest ones, not footnotes:
time and usage but not the
model, so a session that switched models mid-way prices every step at the most recently used model's rates.x-dsh-auth-token (not Authorization: Bearer), and DSH already
holds that grant via getPlatformSession(). It is deferred here because the browser half of a Remote needs
generated zod codecs.pnpm test # tsc --noEmit && node --test test.ts
pnpm typecheck # the type check alone
Types without a build step. client.js ships as plain JavaScript on purpose: the harness injects plugin
bundles into the page as a classic script (<script src>, no type="module"), so the file reaches
the JS engine verbatim. There is no build step and no runtime type stripping on the browser side.
Types therefore live in JSDoc annotations, verified by tsc --checkJs. Real, CI-visible checking with no
toolchain. test.ts is different — Node strips its types natively.
The suite pins the behaviour that matters:
MIT — see LICENSE.