DeepSeek Harness Plugin

dragonestdwolf/dsh-token-workbench

Category Usage & Billing Added 2026-10-27

Token usage workbench for token-plan users: folds assistant/message usage from the session log into per-day call-level detail (cross-session responseId dedupe keeps fork/resume copies counted once), converts local volume into plan credits against terms you enter (default 1M tokens = 0.2 credits, caps 600/2500/6000 for day/week/month, optionally scoped to selected channels), and shows a composer-dock readout plus a settings page with per-provider cost table, 7/30d bar and line trends and a rolling six-month heatmap. No credentials are read: the remaining percentage a provider keeps behind its control-plane API is replaced by a clearly labelled local conversion, and reference costs come from the public DeepSeek pricing page.

Install

# from a prebuilt release tarball

dsh plugin --profile web add "https://github.com/dragonestdwolf/dsh-token-workbench/releases/download/v0.3.0/dsh-token-workbench-0.3.0.tgz"

# from GitHub (first run asks for allowBuilds approval — follow the hint, retry)

dsh plugin --profile web add github:dragonestdwolf/dsh-token-workbench

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).

Links

More in this category

View the whole category →

Community comments

Comments are public GitHub Discussions. Loading them connects to GitHub and Giscus; a GitHub account is required to post.