dsh-custom-mode#editor
Custom modes / assistant manager: give each mode its own system prompt in the settings page — a custom prompt that is a plain file the agent loop re-reads before every model step, so an edit applies to the running session on its next step — and start it from the official standard / PTC / minimal / Cordis composition, toggling the plugin rows it mounts one by one (a custom plugin composition per mode), renaming it as you like. Several assistants coexist with their own prompts, so one machine can keep a coding assistant, a chat companion and a roleplay (RP) persona side by side — a multi-agent setup you pick from per new session. Rows left untouched stay byte-identical to the shipped ones, platform conditions included.
On this page
Review info: no independent structural review record is currently matched.
Community signals
Category
Identity & Communication
GitHub stars
2
npm downloads
3,412
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
- Confirm package.json, the bundle patch and README belong to the same author repository.
- Inspect preinstall/install/postinstall/prepare, child_process, shell, filesystem, network calls and credential access.
- First install into a disposable profile/workspace without production credentials or an important repository.
- If pnpm asks for allowBuilds/build approval, treat it as permission to execute third-party code during installation; do not approve mechanically.
- For reproducibility, pin an exact npm version or Git commit yourself instead of depending on main/latest.
“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.