asdf17128/dshp

Registers list_profiles and export_profile, so the agent can show what setups exist and hand back a whole profile — bundle order, plugin versions and patch — as one portable file to share. Read-only.

Hands a whole dsh setup to someone as one file, and gives it back as the same tree. dshp ls and dshp show answer what is installed and in what order without opening a file (read-only, zero dependencies); dshp clone web web-test duplicates a working profile — node_modules included — in under a second so you can experiment on the copy and delete it; dshp export writes bundle order, plugin versions and your patch into one short file, and dshp import rebuilds it. The README reports a verification where a 132-entry profile was reproduced into a fresh $DSH_HOME and composed an identical tree, patch included.

Tools & Capabilities ★ 3 updated 2026-08-29
View on GitHub ↗

Install

dsh plugin --profile web add github:asdf17128/dshp

README's install/uninstall lines quoted verbatim (dsh plugin --profile web add github:asdf17128/dshp / dsh plugin --profile web remove dshp). The CLI form needs no install at all: the README's own examples run npx github:asdf17128/dshp ls (registry check 2026-09-16: no dshp package on npm, so the GitHub npx form applies and no npm version is asserted).

Compatibility

README: verified against @deepseek-ai/dsh 0.1.0-rc.5. It reads the profile layout dsh itself owns — package.json with dsh.profile.bundles plus cordis.patch.yml — and the README names that as the first thing a future dsh change would break. Repo verified 2026-09-16 (3★, MIT, last push 2026-08-29).

Details

Recent updates

The README documents the command set and the profile model rather than a release-by-release table.

FAQ

Do I have to install anything to try it?
No — the README's examples use npx github:asdf17128/dshp ls, which is read-only and dependency-free. The bundle form dsh plugin --profile web add github:asdf17128/dshp is for permanent installation.
What is a dsh 'profile' here?
Per the README it is a package layout: package.json dependencies are the plugins, dsh.profile.bundles is the ordered layer stack, and cordis.patch.yml holds your own id-targeted overrides; cordis.yml and pnpm-workspace.yaml are regenerated boilerplate.
Which harness version is it verified against?
The README states verification against @deepseek-ai/dsh 0.1.0-rc.5, and notes the profile layout it reads is dsh's own, so a layout change there would break it first.

More plugins in Tools & Capabilities

Browse more in Tools & Capabilities

Guides for Tools & Capabilities plugins