DeepSeek Harness plugin

dsh-usage-monitor

Settings usage dashboard: tokens, requests, output tokens, and cache-hit rate from session logs, with a stacked chart and a breakdown table by provider, model, or workspace.

Jump to install

Source facts

Repository
NOirBRight/dsh-usage-monitor
Latest update
Aug 18, 2026
Category
Usage & Billing
GitHub stars
2

Install

Start with a prompt that asks an agent to read the source. Switch to the command if you want to install it yourself.

Copy this prompt into DSH, Codex, or another agent and ask it to read the page and repository first.

Do not install anything yet. Read this DeepSeek Harness plugin and explain what it does, which files, networks, or credentials it can access, and how to install and remove it.

Plugin page: https://deepseekplugins.org/plugins/NOirBRight/dsh-usage-monitor
GitHub: https://github.com/NOirBRight/dsh-usage-monitor
Plugin: dsh-usage-monitor
Author: NOirBRight
Install command: dsh plugin --profile web add github:NOirBRight/dsh-usage-monitor

Do not run the install command until I confirm.

Check the source files

Read the README and other files from this plugin directory before installing.

File explorer3 files
README.mdSource · read only

dsh-usage-monitor

English | [中文](README.zh.md)

Usage dashboard for DeepSeek Harness. It folds provider-reported token usage out of session logs and charts it in Settings.

![Settings → Usage: tiles, stacked chart, and provider table](docs/screenshots/settings-usage.png)

What it shows

  • Tokens, requests, output tokens, and cache-hit rate
  • Stacked chart with Metric (token / request), By (provider / model / workspace), Group (day / week)
  • Week, month, and custom ranges
  • A breakdown table that follows the current By grouping

Subscription quotas are not fetched.

Installation

DeepSeek Harness 0.1.0-rc.6 or later is required. Install directly from GitHub:

dsh plugin --profile web add github:NOirBRight/dsh-usage-monitor#v0.1.0
dsh web

The repository tracks release-ready lib artifacts, so GitHub installation needs no build-script allowlist. A source checkout can use a link installation after running pnpm run build.

Then open Settings → Usage.

Data

Reads ctx.sessionQuery (live + persisted sessions). Does not scan session.jsonl.zstd itself and does not read leftover community cache files.