dsh-cache-stabilizer

The DeepSeek provider-side prompt cache only triggers on an exact prefix match starting from token zero, yet the default DSH behavior bakes the working directory into the persona sentence of the system prompt. Every time you switch projects the prefix changes, the cache misses, and you pay again for tokens you have already sent. dsh-cache-stabilizer exists to remove that friction.

The plugin makes two semantics-preserving changes. First, it relocates the working directory out of the known default persona sentence and into the runtime-context snapshot, so different projects can share the same system-prompt prefix while each request still receives the correct cwd. Second, it canonicalizes the object-key order inside tool schemas, eliminating another source of non-deterministic noise in the cacheable prefix. On top of that, a human-only /cache command lets you read the actual provider cacheReadTokens, uncached inputTokens, and cache-write tokens, so you can verify cache behavior at a glance instead of guessing.

If you run multiple projects through DSH and want to cut down on repeated DeepSeek billing, this plugin is worth a try. Its safety boundary is tight: only the exact sentence used by the standard headless coding persona is relocated; a custom persona that mentions {{cwd}} in another form is left untouched. The plugin does not freeze tool catalogs, reuse stale context, proxy model responses, or implement a second cache.