Foreword

In the DSH plugin ecosystem, a prompt-activation / trajectory-anchor plugin can easily mix guidance, tool exposure, lifecycle, and task orchestration together. The approach taken by mv-superds is deliberately consolidated: it only handles matters related to the first-round tool exposure and trajectory-mode lifecycle, without extending to cognition protocol, task routing, or workflow orchestration.

Below is an introduction to its positioning, core capabilities, installation method, and typical usage.

What is it

mv-superds is a deliberately minimalist DSH prompt-activation / trajectory-anchor plugin, maintained by aitingtingya, licensed under MIT.

It automatically provides after installation:

  • mv-Standard Mode
  • mv-PTC Mode
  • mv-Creative Mode
  • /mv-superds persistent trajectory-mode command

Its responsibility boundaries are quite clear:

  • Support Pro / Flash independent selection of Weak / Normal / Force, defaulting to Normal for both.
  • Control the exposure of first-round official built-in tools and external/third-party tools, as well as epoch / DSH turn lifecycle.
  • All modes restore the full tool directory after the first durable tool/call.
  • Not responsible for cognition protocol, agent behavior framework, task routing, or workflow orchestration.
  • No special compatibility logic for any specific Skill or other plugins.

Core Features

Trajectory Mode

mv-superds supports Pro / Flash independent selection of Weak / Normal / Force, defaulting to Normal for both.

Weak / Normal / Force mainly affects two things:

  1. The scope of exposure for first-round official built-in tools and external/third-party tools;
  2. epoch / DSH turn lifecycle.

Regardless of the selected mode, the full tool directory is restored after the first durable tool/call.

Commands and Presets

The plugin provides the /mv-superds command, supporting the following subcommands:

  • status
  • pro weak
  • pro normal
  • pro force
  • flash weak
  • flash normal
  • flash force

Bare /mv-superds and /mv-superds status are both used to view the current Pro / Flash status.

The command supports the --preset advanced directional parameter:

/mv-superds pro weak --preset mv-standard
/mv-superds status --preset mv-standard

preset ID only allows lowercase letters, numbers, and hyphens, and cannot traverse outside .agent-presets via path segments.

Without --preset, mode modifications apply to all mv-superds managed presets under $DSH_HOME/.agent-presets that have the .mv-superds-version tag.

The command only modifies the target model’s mode:, it will not overwrite existing custom guidance.

Installation and Enablement

Building and Installation

First, execute the plugin build:

npm run build:plugin

Then install it to the target profile. Taking the web profile as an example, replace the path with your absolute path:

dsh plugin --profile web add file:/绝对路径/mv-superds-开发/plugin

After installation, restart the DSH web process, or refresh according to DSH’s plugin reload method.

Loader Row Note

mv-superds declares the loader row via dsh.bundle.patch, allowing direct installation to the target profile.

If there is a manually maintained cordis.patch.yml in the profile, do not add mv-superds to it simultaneously to avoid ID conflicts.

If force: true appears in the configuration at the installer level, it only indicates that the installer forcibly overwrites manually managed preset directories without version tags; it is unrelated to the trajectory Force mode.

Configuration and Effectiveness

Configuration is persisted to:

$DSH_HOME/.agent-presets/<preset-id>/agent.cordis.yml

Supports the following models configuration:

  • default
  • deepseek-v4-pro
  • deepseek-v4-flash

Under each model, mode and guidance can be configured. The matching order is:

provider/model > model > default

Old force: / opener: configurations can still be read and automatically migrated.

New sessions will use the new configuration; currently mounted sessions will continue to use the configuration at the time of mounting.

Windows

Windows first anchor continues to use Git Bash fallback, tool name remains bash.

If you need to specify a Git Bash path, you can use:

MV_SUPERDS_GIT_BASH

Applicable Scenarios and Notes

Suitable for scenarios where you need to control first-round tool exposure and trajectory-mode lifecycle in DSH, and wish to keep the plugin boundaries very narrow.

Points to note before using:

  1. The plugin runs with the current dsh process permissions; you should check the source code and license before installation.
  2. mv-superds is not responsible for cognition protocol, agent behavior framework, task routing, or workflow orchestration.
  3. suppressSources is just a general profile-driven filter, not special handling by this plugin for specific tools or Skills.
  4. The command will modify the target model’s mode:, please confirm the target preset fits expectations before executing.

Getting

GitHub Repository:

https://github.com/aitingtingya/mv-superds