← Back to list

dsh-cap-profile

DeepSeek Harness Other Low risk

Per-model capability profiling for DSH: turns local session history into per-model dashboards of session counts, tool usage, error rates, and top error signatures, with time-range filters and multi-model comparison.

DSH 按模型的能力画像:把本地会话历史变成逐模型的会话数、工具使用、错误率与 Top 错误签名看板,支持时间范围过滤与多模型对比。

How to install

DeepSeek Harness dsh plugin add github:Ansonfishing/dsh-cap-profile

About

dsh-cap-profile **语言 / Language: 中文 | English** 模型能力画像面板——DSH(DeepSeek Harness)插件。 为什么 会话跑得越多,越难回答「哪个模型在哪些事上稳、哪些事上老翻车」。翻原始日志太慢,人肉统计容易漏。 这个插件把 ~/.dsh/sessions 的会话历史做成画像,直接回答:每个模型的会话数、工具调用量、错误率、最爱用的工具和最高频的错误签名。 快速开始 **前提**:DSH(带 web)+ pnpm;Node ≥ 24(zstd 解码用 Node 内置 zstdDecompressSync)。 bash cd ~/.dsh/profiles/web # 你的 DSH web profile 目录 pnpm add github:Ansonfishing/dsh-cap-profile 然后在 package.json 的 dsh.profile.bundles 数组里加上 "dsh-cap-profile",重启 dsh。会话视图出现「能力画像」tab;首次打开触发后台首扫(大历史约 20s 级),期间先显示 mock 数据。 功能 **模型对比表**——每个模型(provider / model)的会话数、工具调用数、错误数、错误率。 **工具 Top5 / 错误签名 Top5**——每模型最常用工具(含 p…

Recommendation signals

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

Meta

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

Links

GitHub ↗ Report issue ↗

Basic safety check

Findings
curated 收录但无 npm 包/安装命令
Sources
curated:awesome-dsh-plugin.com, curated:awesome-dsh-plugin/awesome-dsh-plugin
Topics
analytics, dashboard, deepseek-harness, developer-tools, dsh, dsh-plugin, llm, nodejs, observability, plugin, react, session-analysis

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 ↗