@local/dsh-cache-saver
精简每次请求都会重新发送的提示负载：按代理精简过大的工具 JSON Schema，分析工具结果量和历史记录构成，并在设置页面显示由此推导出的等效 token 成本。
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add github:ium9khbep8834-maker/dsh-cache-saver#ab73ebb8bd0d36c19fb5a55f0d5805e35019d70dCache Saver 以 @local/dsh-cache-saver 发布，当前版本为 0.3.1。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
点击下方 Badge 复制 Markdown，粘贴到 README 即可。
验证 package.json 声明的 GitHub 仓库，即可管理这个公开页面。认领后，Hub 会优先安排当前版本的安全扫描，并在通过后公开展示结果。
认领这个 Plugin →Cut the token cost of a large tool set, keep more of every request inside the prompt cache, and measure where the re-sent context actually goes.
A host + client bundle for DeepSeek Harness — no build step, no dependencies.
git clone https://github.com/ium9khbep8834-maker/dsh-cache-saver
Then install it into a profile:
install_bundle with target = the cloned
directory (absolute path).~/.dsh/profiles/<profile>/node_modules/@local/dsh-cache-saver and add one row
to that profile's cordis.yml:- id: cache-saver
name: '@local/dsh-cache-saver'
config: {} # optional, see "Config" below
Restart the app (or reload the bundle) once. The client half is imported during page boot, so the settings entry appears only after a restart / page reload — then open Settings → Cache saver.
Every request re-sends the whole prompt prefix: the tool schemas, the system
sections, and the entire message history. On this machine the tool schemas alone
were 275 tools / ~722 000 chars of parameters JSON (≈180 K tokens) on the
first request — 82 % of it from one MCP server (rea, 207 tools). A handful of
tools were enormous on their own:
| tool | schema chars |
|---|---|
mcp__rea__compare_web_captures | ~155 600 |
mcp__rea__compare_application_versions | ~28 900 |
mcp__rea__inspect_analysis_view | ~27 500 |
mcp__rea__evaluate_reconstruction_coverage | ~24 600 |
mcp__rea__project_managed_application_graph | ~21 200 |
Two facts make this worth attacking:
For every agent it registers a scoped copy of the selected tools whose
parameters is compact but still callable:
{ "type": "object", "additionalProperties": true }
with a short description;examples, default, $comment, title, $id, $schema and similar
annotation-only keywords are dropped;oneOf/anyOf fan-out beyond maxBranches is truncated
with an explicit note;maxSchemaChars (or the tool is added to keepFull).Scoped tools shadow globals (documented tools.register behaviour), while
execute, output, presentCall, presentResult and timeoutMs are copied
from the original definition, so dispatch is unchanged. Registrations are
owned by the agent's own context and the plugin's own ctx.effect, so they
disappear with the agent or on unload.
Measured on the live profile: 158 shadowed tools, 740 692 → 121 190 chars
(−83.6 %, ≈ −154 900 tokens per request). One step of this very session then
billed input 133 164 tokens with 99.5 % cache hit — the surviving prefix is
cached, the money goes into the ~1 400 full-price tokens that changed.
Cost is measured from the provider's own usage numbers, not from a character
heuristic: a char/4 estimate of this profile's history reads ~3× the billed
tokens (it also counts content a compaction fold already replaced), so it would
overstate every card on the page.
tools/result — for every tool outcome: content chars, approximate tokens,
duplicate identical calls, errors, and per-tool totals (never the payload).
session/event + assistant/message — for every billed model call:
usage.inputTokens, usage.cacheReadTokens, usage.cacheWriteTokens,
usage.outputTokens, plus the durable history's per-bucket composition
(user / assistant / tool result / tool-call args / reasoning / other) as a
percentage mix, and two derived numbers:
new_tokens = input_tokens − cache_read_tokens (what is paid at full price)cost ≈ 0.1 × cache_read_tokens + new_tokens (one step priced at the cache-hit rate)The page also shows the billed cache hit rate (cache_read / input) so the
two goals — a high hit rate and a small bill — are visible side by side.
The bundle ships client.js, which contributes one page to the settings panel:
settings.section, id cache-saver, order 45 (between 插件 / 市场 and 哔哩).GET /api/cache-saver/status — read-only route on the host webServer,
same origin, no credentials, cache-control: no-store.Findings are generated, not hard-coded, e.g.:
N tool result(s) exceeded bigResultTokens (largest M) → lower
spill-policy.maxInlineTokens or delegate noisy subagents;maxSchemaChars.Because the client half is loaded from the boot manifest, a page that was open
when the bundle was installed does not see it: refresh once (F5).
The route can be checked without the GUI:
curl -s http://127.0.0.1:52811/api/cache-saver/status
Every key is optional; set them in the row's config in cordis.patch.yml.
| key | default | meaning |
|---|---|---|
shadowPrefixes | ["mcp__rea__"] | only tools with one of these prefixes are slimmed |
keepFull | 8 core mcp__rea__ read tools | exact tool names never slimmed |
minChars | 700 | a schema already this small is only description-clamped |
maxSchemaChars | 800 | target ceiling for a slimmed schema |
maxDepth | 3 | deepest nesting kept; deeper objects become additionalProperties |
topDescriptionChars | 140 | schema-root description limit |
nestedDescriptionChars | 60 | one-level-down description limit |
descriptionDepth | 1 | deeper descriptions are dropped |
maxDescriptionChars | 260 | tool description clamp (0 disables) |
maxBranches | 4 | union branches kept per keyword |
bigResultTokens | 6000 | results above this are counted as "large" |
maxStepSamples | 60 | step snapshots kept per agent for the timeline |
dryRun | false | measure without registering shadows |
Example:
- insert:
- id: cache-saver
name: '@local/dsh-cache-saver'
config:
shadowPrefixes: ['mcp__rea__', 'mcp__some_other_server__']
keepFull: ['mcp__rea__inspect_web_page', 'mcp__rea__analyze_function']
maxSchemaChars: 1200
bigResultTokens: 4000
cache_saver_status — shadowed tools, chars before/after, ≈tokens
saved, tool-result volume, billed steps (input / cached / hit rate), equivalent
cost, recommendations.curl -s http://127.0.0.1:52811/api/cache-saver/status.parameters, and a shadowed definition keeps the original execute. The only
risk is that the model forgets a rarely used nested option — raise
maxSchemaChars / maxDepth, or add the tool to keepFull.dryRun: true measures first.node test/unit.mjs # schema slimming, shadow registration, route, attribution, cost
node test/client.mjs # client bundle: registration shape, page render, error/empty states
Both are dependency-free: they stub the Harness objects they touch and never start a real host or browser.
The app refuses to start with web boot: 1 entry did not activate /
import failed and the renderer console shows
client-modules: duplicate factory registration for "<old id>".
The client module id inside client.js must equal the package name in
package.json (@local/dsh-cache-saver). The web boot imports the bundle by
its package specifier; a different id registers a factory the loader cannot
resolve, so it executes the bundle a second time. Fixed in 0.3.1, which also
wraps the registration so a genuine double execution is an idempotent no-op
instead of aborting the boot.
Recovery if a stale copy still fails: open the crash dialog, choose
禁用第三方插件、备份 profile patch 并重启, then re-enable the bundle from
Plugins settings (or plugin_manager set_bundle on @local/dsh-cache-saver).
MIT — see LICENSE.