dongsheng123132/dsh-cache-stabilizer
针对DeepSeek Harness的缓存前缀稳定性与基于证据的缓存指标
Project Overview项目介绍
dsh-cache-stabilizer is an MIT-licensed DSH plugin that improves provider prompt-cache reuse by moving the working directory out of the default persona sentence into the runtime-context snapshot and canonicalizing object-key order in tool schemas. It also adds the human-only /cache command to report cache-read, uncached-input, and cache-write tokens. Use it when working across projects and wanting stable cache prefixes. It does not fabricate hits; provider caching still depends on exact prefix matching.
dsh-cache-stabilizer 是 MIT 许可的 DSH 插件,通过把默认 persona 中的工作目录移到运行时上下文快照,并规范化工具 schema 的对象键顺序,提升 DeepSeek 提示缓存前缀复用概率;另提供仅人工可用的 /cache 查看缓存读取、未缓存输入和缓存写入 token。适合多项目会话想稳定缓存命中时使用;它不伪造命中,也不处理自定义 persona 中的 cwd 表述,缓存仍由服务商按精确前缀控制。
请帮我安装这个 DSH 插件。安装前先完成【兼容性检查 + 安全性检查】,检查通过再动手。
插件:dsh-cache-stabilizer(dongsheng123132/dsh-cache-stabilizer)
仓库:https://github.com/dongsheng123132/dsh-cache-stabilizer
本站详情页:https://www.yhbd.top/plugins/dongsheng123132-dsh-cache-stabilizer/
本站登记:类型 plugin · 归类 原生 DSH 插件 · 许可证 MIT · ⭐ 2 · 最近提交 2026-09-07 · 主语言 JavaScript
按下面顺序执行,每步先把结论告诉我,再进入下一步:
【1 兼容性检查】
① 我这边:DSH 版本、Node 版本、操作系统、当前 profile(web / desktop)。
② 读它的 README、package.json、插件 manifest,列出它要求的 DSH 版本 / Node 版本 / 操作系统 / 外部依赖 / 需要另外先装的运行时。
③ 逐条比对,结论只写「满足 / 不满足 / 未知」三种;不满足的给出可行替代方案。
④ 检查是否和我已装的插件冲突:命令名重复、skill / tool 重名、端口占用、重复注册的 MCP server。
【2 安全性检查】
① 仓库可信度:和上面「本站登记」是否一致;star / fork 数、创建时间、最近提交,是否归档或长期停更。
② 安装脚本:逐行看 package.json 的 preinstall / install / postinstall,以及 install.sh、setup.ps1 之类脚本。出现 curl|bash、下载后直接执行、混淆代码、访问与插件功能无关的域名,立刻停下来告诉我,不要继续装。
③ 依赖:列出新增依赖,标出无人维护、或与知名包拼写近似的可疑包(typosquatting)。
④ 权限与副作用:它会读写哪些目录、访问哪些域名、需要哪些 DSH 权限(filesystem / network / shell / clipboard 等),以及怎么卸载和回滚。
⑤ 如果它要求 sudo / 管理员权限,或权限明显超出功能所需,先停下来问我。
【3 安装】
上面两步没有「不满足」和「高危项」时才执行;用官方推荐方式安装,不要自行提权。
【4 汇报】
用表格输出:检查项 / 结论 / 依据 / 是否需要我决策。拿不准的一律写「未知」并说明要我怎么确认——不要猜,也不要替我决定。
Send this message to DSH in your current session: it verifies compatibility and security first (answering met / not met / unknown item by item) and only installs once everything checks out — it will stop and ask you if it finds a high-risk item. The box scrolls; the copy is the full prompt. CLI install commands may not be accurate across systems, so DSH is the safer route.把上面这条消息直接发给当前会话里的 DSH:它会先核对兼容性与安全性(逐条给「满足 / 不满足 / 未知」),确认没问题再安装,有高危项会停下来问你。框内可滚动,复制到的是完整提示词;安装命令不一定准确,发给 DSH 更稳。
- Only 2 stars - very few users, little community feedback星标只有 2,几乎没人在用,遇到问题缺少社区反馈
DSH walks through these 9 checksDSH 会逐条核对这 9 项
Compatibility兼容性
- DSH, Node, OS and profile requirementsDSH 版本 / Node 版本 / 操作系统 / profile 是否满足要求
- External dependencies and runtimes (Electron / Python / Docker, ...)外部依赖与运行时(Electron / Python / Docker 等)是否齐备
- Conflicts with installed plugins: command names, skill / tool names, ports, duplicate MCP registration与已装插件是否冲突:命令名、skill / tool 重名、端口占用、重复 MCP 注册
Security安全性
- Repo matches the facts registered here; archived or abandoned?仓库是否与页面登记一致,是否归档或长期停更
- Safety of preinstall / install / postinstall and install.sh / setup.ps1preinstall / install / postinstall 与 install.sh、setup.ps1 是否安全
- curl|bash, download-then-execute, obfuscation, unrelated domains → stop immediatelycurl|bash、下载即执行、混淆代码、无关域名 → 立刻停止
- Typosquatting or unmaintained packages among the new dependencies新增依赖里有没有 typosquatting 或无人维护的包
- Requested permissions vs. what the feature actually needs申请了哪些权限、是否超出功能所需(filesystem / network / shell / clipboard)
- Any sudo / admin requirement, plus uninstall and rollback是否要求 sudo / 管理员权限,以及卸载与回滚方式
Anything uncertain must be marked unknown with a note on how to confirm it. This site's signal screen is a static snapshot, not a security audit.拿不准的必须标「未知」并说明要我怎么确认。本站的信号筛查是静态快照,不能替代安全审计。
Or use CLI install (for developers)或使用命令行安装(适合开发者)
CLI Install命令行安装
dsh plugin --profile web add dsh-cache-stabilizer
把 dongsheng123132/dsh-cache-stabilizer 加入你的 DSH 配置(web profile)即可启用。
READMEREADME
dsh-cache-stabilizer
An MIT-licensed DeepSeek Harness plugin that improves the chance of provider prompt-cache reuse without hiding stale state.
It makes two semantics-preserving changes:
- Moves the working directory out of DSH's known default persona sentence and into the runtime-context snapshot. Different projects can then share the same system-prompt prefix while each request still receives the correct
cwd. - Canonicalizes object-key order inside tool schemas. Tool order itself is already deterministic in DSH.
It also adds /cache, a human-only command that reports the provider's durable cacheReadTokens, uncached inputTokens, and cache-write tokens. It never invents a cache hit.
Install
dsh plugin --profile web add dsh-cache-stabilizer
Restart DSH, send a few messages, then enter /cache in a command-capable client.
For a custom profile, replace web with its profile name. To disable either optimization in a profile patch:
- id: dsh-cache-stabilizer
config:
relocateCwd: false
canonicalizeTools: false
Safety boundary
Only the exact sentence used by DSH's standard/headless coding persona is relocated. A custom persona that mentions {{cwd}} in another form is left unchanged because blindly moving arbitrary prose can change meaning. The plugin does not freeze tool catalogs, reuse stale context, proxy model responses, or implement a second cache.
DeepSeek's provider cache is automatic and depends on an exact prefix match from token zero. Storage and eviction remain provider-controlled.
Development
npm test
npm run check
alaliqing/claude-paper
qkycir-123/dsh-run2skill
PKUfudawei/dsh-capability-menu
houyanchao/dsh-timeline
a735624258/dsh-skill-picker
Chael-Chael/dsh-reference-anything