Custom DSH plugins for DeepSeek Harness (DSH), maintained by sredevopsorg.
Each directory under plugins/ is a self-contained Cordis plugin package installable into a DSH profile. The repository also publishes index.json, a format-1 plugin market index browsable from the Web Plugins → Discover tab via Custom plugin indexes.
| Plugin | Kind | Use it for |
|---|---|---|
agent-opencode |
bundle + agent preset | Delegates every task to the OpenCode CLI |
code-editor |
bundle + web editor | Right-sidebar workspace file browser and editor |
peak-rate-footer |
bundle + web footer | Peak/off-peak API billing footer with local clock |
skills |
bundle + 10 skills | Packaged skill provider serving 10 agent skills |
sredevops-writer |
bundle + agent preset | Editorial agent preset for sredevops.org |
subagent-opencode |
bundle + subagent provider | Delegates one-shot tasks to OpenCode over ACP |
superagent |
bundle + web panel | Proactive agent that runs GitHub tickets in DSH sessions |
agent-opencode and subagent-opencode are two halves of the same idea,
shipped as independent packages:
subagent-opencodeis the capability. It registers theopencodeprovider and thesubagent_opencodetool, and it works alone.agent-opencodeis the opinionated consumer. It declares an agent preset that may only delegate, and it binds the provider nameopencode-preset.
Neither installs the other, neither imports the other, and each is released
separately. They are safe to install in one profile: no row id, tool name, or
provider name is inserted twice. The preset gets its provider through a profile
patch that ships with it (plugins/agent-opencode/profiles/preset.cordis.patch.yml):
# The capable profile: OpenCode configured, provider registered
dsh plugin --profile web add ./plugins/subagent-opencode
# The driving profile: the preset, plus the provider row it binds
dsh plugin --profile web add ./plugins/agent-opencodeThen add the rows from profiles/preset.cordis.patch.yml to the driving
profile's cordis.patch.yml. Each plugin's README explains the details. The
rule of thumb is that the preset is the policy and the subagent is the mechanism.
-
Open Plugins in the Web sidebar and switch on Custom plugin indexes under Experimental plugins.
-
Select Discover → Add index source and enter:
https://raw.githubusercontent.com/sredevopsorg/dsh-plugins/main/index.json -
Pick a plugin and version and confirm the install. Each entry pins its exact Git commit.
dsh plugin --profile web add "github:sredevopsorg/dsh-plugins#<plugin>-v<version>&path:/plugins/<plugin>"Quote the spec so the shell does not interpret &. Replace web with your profile. Examples:
dsh plugin --profile web add "github:sredevopsorg/dsh-plugins#agent-opencode-v0.3.0&path:/plugins/agent-opencode"
dsh plugin --profile web add "github:sredevopsorg/dsh-plugins#code-editor-v0.1.0&path:/plugins/code-editor"
dsh plugin --profile web add "github:sredevopsorg/dsh-plugins#peak-rate-footer-v0.1.0&path:/plugins/peak-rate-footer"
dsh plugin --profile web add "github:sredevopsorg/dsh-plugins#skills-v0.2.0&path:/plugins/skills"
dsh plugin --profile web add "github:sredevopsorg/dsh-plugins#sredevops-writer-v0.1.1&path:/plugins/sredevops-writer"
dsh plugin --profile web add "github:sredevopsorg/dsh-plugins#subagent-opencode-v0.3.0&path:/plugins/subagent-opencode"
dsh plugin --profile web add "github:sredevopsorg/dsh-plugins#superagent-v0.1.2&path:/plugins/superagent"For local development, install a checkout instead:
dsh plugin --profile web add ./plugins/code-editordsh --profile web list shows installed packages; dsh --profile web --dump-config composes the tree without booting.
plugins/
├── agent-opencode/
├── code-editor/
├── peak-rate-footer/
├── skills/
├── sredevops-writer/
├── subagent-opencode/
└── superagent/
Each plugin ships its own package.json, cordis.patch.yml, entry point, tests, locale, and README.md. Full per-plugin docs live under each plugins/<name>/ directory.
node scripts/validate-bundles.mjs
node scripts/validate-github-install.mjs --strict
node scripts/build-market-index.mjs --check
node scripts/validate-market-index.mjs
node scripts/validate-plugin-pair.mjsCI runs these validators plus the plugin unit tests on every push and pull request.
A release is one annotated tag named <plugin-directory>-v<version>. Bump version in plugins/<dir>/package.json, run the validators, commit on main, and push. The version-plugins.yml workflow tags the release and opens a pull request that republishes index.json.
Or tag by hand:
node scripts/release-tag.mjs --plugin code-editor --pushReleased under the MIT License. Third-party attribution is listed in NOTICE.md.