← Back to list

dsh-minimax-usage

DeepSeek Harness Other High risk

DSH (DeepSeek Harness) plugin: MiniMax Token Plan usage in Settings

在 DSH 设置页「用量」section 展示 MiniMax Token Plan 的 5 小时 / 周窗口用量(带重置倒计时)、单模型明细与视频赠送额度;通过 trusted plugin 调 `/v1/token_plan/remains` 拿 key,未配置 key 时整段 section 自动隐藏。MIT。

How to install

DeepSeek Harness dsh plugin add github:Floating-Dreaming/dsh-minimax-usage

About

MiniMax 用量插件 在 DSH(DeepSeek Harness)设置页「用量」section 展示 MiniMax Token Plan 的 5 小时与周窗口用量。 这是什么 DSH 插件,在设置页的「用量」section 渲染 MiniMax Token Plan 实时数据: **5 小时窗口**:当前用量百分比 + 剩余时间 **周窗口**:当前用量百分比 + 重置倒计时 **视频赠送**:可调用次数(video 模型按 count 计,不按百分比) **未配置 API key 时整段 section 自动隐藏**(侧栏「用量」入口也不显示) 数据通过 MiniMax 的 https://www.minimaxi.com/v1/token_plan/remains 接口实时获取(trusted plugin 持有 key、60s 缓存 + 10s 限流)。 安装 两种方式,**任选其一**。 方式一:DSH 官方 dsh plugin add trusted-plugin/ 声明了 dsh.bundle manifest,DSH 官方安装命令直接认: sh 从 GitHub(git 源一行) dsh plugin --profile web add "github:Floating-Dreaming/dsh-minimax-usage#main" 从 npm dsh p…

Recommendation signals

36 Tool quality · Based on stars, downloads, maintenance, security and docs
– User interest · Adjusted by in-site views, install copies and download clicks
36 Overall
0views
0unique visitors
0install copies
0download clicks
0outbound clicks

Meta

License
–
Language
JavaScript
GitHub stars
2
mo. downloads
–
Last push
2026-08-15
Created
2026-08-15

Links

GitHub ↗ Report issue ↗

Basic safety check

Findings
curated 收录但无 npm 包/安装命令;无 license
Sources
curated:awesome-dsh-plugin/awesome-dsh-plugin
Topics
cordis, deepseek-harness, dsh, dsh-plugin, minimax, trusted-plugin

Related plugins

DeepSeek Harness
Score73

TokenLedger

zh667/TokenLedger

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.

☆ 202 ↓ 1.4K Other ↗
DeepSeek Harness
Score71

dsh-context

bowenliang123/dsh-context

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.

☆ 1.5K ↓ 79.7K Other ↗
DeepSeek Harness
Score69

dsh-usage-statistics-panel

HaoyueQin/dsh-usage-statistics-panel

Usage statistics settings panel: 26-week activity heatmap, daily token trend with a cache hit-rate curve, per-model donut and breakdown, time-range filters, summary cards, one-time historical backfill and lossless rebuild.

☆ 9 ↓ 3.3K Other ↗
DeepSeek Harness
Score68

dsh-all-usage

ParticleLight/dsh-all-usage

Analyze usage across models, providers, workspaces, and time ranges — including custom start/end dates over the full retained history — with live cache-hit visibility and separate model and provider breakdowns. Includes hourly single-day trends, daily cross-day trends, a 53-week GitHub-style heatmap, usage streaks, model and workspace Token-share donut charts with Token, cost, and percentage details, independent combinable filters, cache-efficiency trends, DeepSeek account balance, workspace aliases, CSV export, and a durable ledger that preserves successfully flushed usage after session deletion — and after a workspace is deleted, where its recorded usage is summed into one Deleted row — and rebuilds incrementally — on restart, unchanged sessions are applied from the ledger without re-reading their logs (a per-session log revision is the change signal), and only changed/new events are folded. The workspace registry is kept fresh automatically through the DSH domain/changed probe: only added/removed workspaces are reprocessed incrementally, unchanged workspaces reuse their computed aggregates and ledger with zero rescan, and usage is strictly limited to DSH-registered workspaces (unregistered cwds are ignored). After a scan, lightweight revision status fetches full history only when the Host/data state changes and exposes non-sensitive sync health (revision reuse, rereads, ledger recovery, and failures). Token accounting is explicit: input is fresh (cache read/write and reasoning are separate buckets) and zero-usage replays never overwrite recorded usage. Chinese uses local time, English uses UTC; API access is loopback-only.

☆ 8 ↓ 2.8K Other ↗