DeepSeekDSH
Independent community guideNot affiliated with DeepSeek.Official source snapshot

dsh-context-compression-improved

Same-origin in mechanism with the two loudest lines in context compression. The code-skeleton gate follows the skeletonization approach of Headroom (Apache-2.0), whose published headline is 20% fewer tokens for coding agents and 60–95% fewer tokens for JSON, same answers. The estimator channel follows TokenPilot (arXiv:2606.17016), which reports up to 60% lower cost for long-session agents. Both figures are theirs, quoted as-is; this plugin ships no benchmark of its own and claims no reduction of its own. What it adds for DeepSeek Harness: choose a compression profile, set the Auto Compact trigger level and toggle code-skeleton compression from one settings section, with exact DeepSeek V4 tokenizer measurement, same-revision count verification, and fail-open behaviour that keeps the original tool results on unsupported models.

Independent editorial review: DeepSeekDSHSource checked: 0.1.5-rc.2 · 2026-09-11
On this page
Third-party

Review info: no independent structural review record is currently matched.

Community signals

Category

Sessions & Messages

GitHub stars

1

npm downloads

786

Discovery registry added

2026-09-18

Review information

Scanner status

No review data

Review mode

No review data

Last checked

No review data

Build approval required

No review data

Lifecycle scripts

No review data

Runtime artifacts committed

No review data

Documented profiles

No review data

Why this site does not provide the install command

A third-party DSH plugin is executable local code. Even when structural review evidence exists, registry data, stars and metadata cannot prove the code is non-malicious. Read the current author repository and perform your own review in a disposable environment.

Install and usage source

This site links to the author's source, npm page and community registry instead of redistributing commands. A plugin may add Web UI, Settings, agent tools or background capabilities; follow the author README for the actual entry point.

Minimum checks before install

  1. Confirm package.json, the bundle patch and README belong to the same author repository.
  2. Inspect preinstall/install/postinstall/prepare, child_process, shell, filesystem, network calls and credential access.
  3. First install into a disposable profile/workspace without production credentials or an important repository.
  4. If pnpm asks for allowBuilds/build approval, treat it as permission to execute third-party code during installation; do not approve mechanically.
  5. For reproducibility, pin an exact npm version or Git commit yourself instead of depending on main/latest.
Third-party does not mean unsafe, and review is not a security certification

“Third-party” only means the plugin is not an official DeepSeek plugin. Structural checks improve transparency but cannot prove business logic is non-malicious or fully audit dependencies, future updates or runtime behavior.

Sources

THIRD-PARTY PLUGINSSearch the live registry
Community Plugin Explorer →