@mzzsfy/dsh-tool-gate

Q: Does it collide with dsh-tool-database?

For @mzzsfy/dsh-tool-gate the recommendation is dsh-tool-database: Keep the database tool and add it to the gate whitelist; removing the gate would give up the prompt savings on every other turn.

Q: What happens when dsh upgrades?

Nothing declares a version window for @mzzsfy/dsh-tool-gate: dsh --version tells you what you are running, and no check will tell you whether @mzzsfy/dsh-tool-gate matches it.

Keeps tool definitions out of the request until they are whitelisted, cutting prompt weight.

Version 0.2.4 of @mzzsfy/dsh-tool-gate, last published 2026-11-13; the install command and the range come from its own manifest.

Install

dsh plugin add @mzzsfy/dsh-tool-gate writes one dependency line into the profile manifest; pnpm then unpacks it under $DSH_HOME/profiles/<name>/node_modules.

dsh plugin --profile web add @mzzsfy/dsh-tool-gate

Compatibility

@mzzsfy/dsh-tool-gate ships no engines.dsh entry, so nothing checks it against your CLI version at boot. Read the npm page before installing.

If two plugins fight

A tool gate: everything outside its whitelist is deferred. @logictan/dsh-tool-surface trims the same tool list by a different mechanism — two gates means tools can be deferred by one and never loaded by the other.

Who made it

Author: mzzsfy. Repository: https://github.com/mzzsfy/dsh-plugin. Package page: https://www.npmjs.com/package/@mzzsfy/dsh-tool-gate.

After install

It declares @deepseek-ai/cordis as a peer and renders a new callable tool in the tool list; after dsh plugin add @mzzsfy/dsh-tool-gate, dsh --profile web --dump-config lists the row that mounts it.

Files it touches

No storage peer appears in the manifest of @mzzsfy/dsh-tool-gate, so the dependency line in $DSH_HOME/profiles/<name>/package.json is the only file you can point at; the package description names nothing else.

Removing it

Removing @mzzsfy/dsh-tool-gate is the mirror command, dsh plugin --profile web remove @mzzsfy/dsh-tool-gate. Its manifest declares no storage peer, so it writes nothing under $DSH_HOME; removing it leaves no files behind.

Common questions

Does it collide with dsh-tool-database?

For @mzzsfy/dsh-tool-gate the recommendation is dsh-tool-database: Keep the database tool and add it to the gate whitelist; removing the gate would give up the prompt savings on every other turn.

What happens when dsh upgrades?

Nothing declares a version window for @mzzsfy/dsh-tool-gate: dsh --version tells you what you are running, and no check will tell you whether @mzzsfy/dsh-tool-gate matches it.