DeepSeek Harness Plugin Hub

发布与管理完整 Harness Profiles,发现适合你的插件。

探索

插件目录环境预设文档中心动态

社区

发布插件联系我们报告问题

相关链接

Plugin Hub GitHubDeepSeek Harness 官方项目系统状态隐私说明
© 2026 DeepSeek Harness Plugin HubPowered byPaxTech

独立、非官方社区项目,与 DeepSeek 官方无隶属、授权或背书关系。

Cache Hit Monitor — DeepSeek Harness 插件(DSH Plugin)
DeepSeek Harness Plugin Hub
ProfilesPlugins分类动态文档登录管理 Profiles
ProfilesPlugins分类动态文档登录
← Plugins
C

dsh-cache-hit-monitor

Cache Hit Monitor

DSH 右侧边栏中当前会话的实时 prompt-cache 遥测:寄存器组、点阵命中率和反应堆核心历史面板。

插件会安装到这里;不确定时保持 web。

npx -y @deepseek-ai/dsh plugin --profile web add github:Billwu18/dsh-cache-hit-monitor#391b2ac76a421891199b7f0bf9dc41836185e7d2
README兼容性版本
Cache Hit Monitor, dark theme

兼容性与来源证明

Cache Hit Monitor 以 dsh-cache-hit-monitor 发布,当前版本为 1.0.0。Plugin Hub 会校验它的 manifest,并保存精确安装来源,便于复现安装结果。

DSH 兼容范围
*
运行环境
web
发布来源
github
Registry 更新时间
2026/9/26

版本

1.0.0stable
2026/9/26

相关插件

正在加载相关插件…

最新版
1.0.0
DSH
*
HMR
重启进程
Tree shaking
未声明可安全裁剪
解包体积
未提供
文件数
未提供
Surface
web
许可证
MIT
发布源
github
GitHub
★ 0
周下载
0
最近提交
2026/9/26
查看源码 ↗
README Badge

点击下方 Badge 复制 Markdown,粘贴到 README 即可。

这是你的 Plugin?认领权益 · 优先安全扫描

验证 package.json 声明的 GitHub 仓库,即可管理这个公开页面。认领后,Hub 会优先安排当前版本的安全扫描,并在通过后公开展示结果。

认领这个 Plugin →
报告问题

相关插件

继续浏览 ui-customization 分类下经过校验的插件。

Web App@deepseek-ai/dsh-web-appdsh 浏览器界面捆绑包:位于 dsh-base 之上的 Web 补丁层,加上运行时粘合插件(提供前端 dist、Web 界面提示符、bash 运行时变量和 URL 行)Experimental Agent Team Web Profile@deepseek-ai/dsh-experimental-agent-team-web-profile用于 Agent Teams Remote 和 UI 插件的实验性 Web 配置层Ab Chartdsh-ab-chart带有绘制其调用的浏览器卡片的图表渲染工具,封装在一个可发布的插件包中Whale Widgetdsh-whale-widgetDSH Web 界面右下角的 DeepSeek 余额小鲸鱼挂件:余额/今日已用/峰谷定价、自定义泡泡点击序列(文本/余额/今日/峰谷/图片/随机语句与并列加权选择)、逐行样式与字体、悬浮快捷编辑、音效与每轮消耗、自定义角色/动图/音效、吸附与翻转自定义

README

Cache Hit Monitor

Live prompt-cache telemetry for the current session, drawn as an instrument panel in the DSH right sidebar.

English · 中文说明

Cache Hit Monitor, dark theme


What it does

The plugin adds one tab to the DSH right sidebar. It reads the tokenUsage and contextPressure session projections the Host already publishes and shows them as four flat instrument faces:

FaceShows
Hit rateSession cache-hit rate as a 5×7 dot-matrix percentage, plus the settled request count, the last request's rate, that request's age and a 28-lamp bar against the current prompt total.
Register bankThe four disjoint cache buckets — cache read, cache write, uncached input, output — with session totals and proportional lamp rows.
Reactor coreOne cell per settled request, newest first. Ink is that request's cache-hit rate, diameter is its size against the heaviest request on the board, and the field fades with age.
Context pressurePressure tokens against the context window.

The tab opens by itself once per page load, so the panel is on screen without hunting through the tab guide. It closes like any other tab.

How the hit rate is calculated

hit rate = cache read / (cache read + cache write + uncached input)

Output tokens are deliberately excluded. Generated tokens are never cacheable, so counting them would flatter the number — a long generation would make a cold prompt look warm.

The reactor core in detail

One cell is one request that settled while the panel was mounted, ordered newest-first from the top left. The board is one whole number of rows at all times, and it is never taller than the history it actually holds, so a young session shows a short row rather than a large empty lattice.

  • Ink — the request's hit rate, on a single-hue intensity ramp.
  • Diameter — sqrt(request tokens / heaviest request on the board), which keeps small requests visible next to a cold burst.
  • Fade — older cells dim toward the bottom of the board.

Each cell carries a title with its exact read / write / uncached / output split, so the picture can be audited rather than trusted.


Install

From GitHub

dsh plugin --profile web add github:Billwu18/dsh-cache-hit-monitor

Or install it through the Plugin Manager in the Web UI.

Manual, for development

git clone https://github.com/Billwu18/dsh-cache-hit-monitor
dsh plugin --profile web add /absolute/path/to/dsh-cache-hit-monitor

Then reload the page. The Host re-reads plugin artifacts by modification time, so edits to client.js are picked up by a refresh — no dsh web restart.

Requirements

  • DSH >=0.1.7-rc.1 <0.2.0-0
  • Node >=20 (only for the test harnesses; the plugin itself runs in the browser)
  • React 18 or newer, which the DSH Web UI provides

No dependencies, no build step, no install scripts.


Reading the instrument

  • A filled red dot next to the title means at least one request has settled in this session; an empty ring means nothing has been recorded yet.
  • The register bank shows session totals, not per-request values. Its lamps are proportional to the largest bucket on screen.
  • The core legend (0 % → 100 %) is the ink ramp, so a cell's brightness can be read back as a number.
  • ROWS 4 / 6 / 9 sets the maximum board height in rows. The width is chosen by the sidebar itself: the panel measures how many columns fit and the board grows into whole rows, so the same history fills more rows in a narrow sidebar than in a wide one.
  • CLR clears the recorded history for the current session. It does not touch any Host-side data.

How it works

The Host half is deliberately inert (index.js exports an empty apply). It exists so the bundle has a Loader row and can be enabled, disabled and inspected like any other plugin.

Everything the panel shows is already computed on the Host: @deepseek-ai/dsh-token-meter folds the durable session log into the tokenUsage and contextPressure projections. The Client half reads them from its slot props via useProjection and renders.

The client bundle is a single file (client.js) in the DSH browser-module format. It uses only React and standard browser APIs:

  • The board measures its own column count from the live layout with getComputedStyle plus a ResizeObserver, and re-renders once before paint. If the measurement is unavailable the board simply grows with the data instead of being capped.
  • The clock for the "age" readout lives in its own component and ticks at the resolution it prints (1 s / 5 s / 30 s), so an idle panel is not reconciling the whole board once a second.
  • Recorded history lives in a bounded module-level cache keyed by session, so it survives the remount that a tab switch causes. The tab is also registered with keepMounted: true, which prevents that remount in the first place.

Privacy

The panel reads local session projections. It makes no network requests, sends no telemetry, and stores nothing outside the browser tab. Clearing history touches only in-memory state.


Compatibility

DSH>=0.1.7-rc.1 <0.2.0-0
Platformweb (dsh.client.platform)
React18 or newer (provided by the host)
ThemesBoth. The instrument faces are intentionally dark in both themes; the surrounding chrome follows the --dsw-* theme tokens.
LocalesEnglish and Chinese. Other locales fall back to English.
HostsAny host that provides the sidebarRightTabs service.

Development

No dependencies are required to work on this plugin — the tests run on plain Node against the real client.js.

node test/run-all.mjs     # all four suites
node test/preview.mjs     # writes HTML that can be screenshotted

Repository layout

dsh-cache-hit-monitor/
├── client.js              the entire browser half (React, DSH module format)
├── index.js               the host half (intentionally inert)
├── cordis.patch.yml       the Loader row that installs the plugin
├── package.json           manifest: dsh.bundle + dsh.client
├── icon.svg               plugin card artwork
├── screenshots.json       storefront screenshots, relative to this file
├── locale/
│   ├── en.json            plugin card title and description
│   └── zh.json
├── assets/                screenshots referenced by the READMEs
└── test/
    ├── run-all.mjs        runs every suite below
    ├── preview.mjs        renders the panel to standalone HTML
    ├── wiring.test.mjs    bundle identity, effects, tab and slot registration
    ├── render.test.mjs    the rendered tree: shapes, counts, no NaN, key coverage
    ├── persist.test.mjs   history and depth survive a remount
    └── robust.test.mjs    adversarial inputs and locale coverage

How the tests work

There is no DOM and no test framework. Each harness stubs window.__ModuleLoader__ to capture the bundle, stubs react, applies the real apply(ctx) against a stub context, then drives the registered component with a small renderer.

That is enough to assert real behaviour: which services the plugin injects, what it registers into which slot, how many cells and lamps the tree contains, that history survives a remount, and that no reachable input produces a thrown exception or leaks undefined/NaN into a style string.

SuiteAsserts
wiringModule id, declared injects, ctx.effect registrations, the tab definition (including keepMounted), both keyed slot registrations, and that the body is a component.
renderRendered tree shape: dot-matrix dots, reactor cells and cell dots, bar lamps, register rows, exactly one red element, no undefined/NaN in any style, and that every element in an array has a React key.
persistA real per-instance hook runtime: record a request, change the depth, unmount, remount — history, depth and keepMounted all confirmed.
robust16 adversarial scenarios (missing or throwing projection, NaN/Infinity/negative/string token counts, no session id, no translate seat, empty to 10 000 events) must all render, and every locale key must exist in both dictionaries.

License

MIT © 2026 Billwu18