Credentials. The agent runs commands in your profile directory, and a plugin it installs can read your filesystem and shell, so limit the profile's access before you let an agent run this.
Who it is forA team lead or developer who wants an agent to set up DSH Plugin Shop on a machine without manual steps.
The problemSetup has several steps that are easy to skip, such as the required --profile option and checking the installed version.
The outcomeThe agent reports the profile it used, the installed plugin version, and whether DSH Plugin Shop is listed for that profile.
What you need first
- Node.js installed, with npm available
- DeepSeek Harness (dsh) installed globally with npm install -g @deepseek-ai/dsh pnpm, or run through npx
- A dsh profile name to use (the README uses web as the example)
- Willingness to trust installed plugins, since they have full access to ctx including the filesystem and shell
Steps
- List available profiles with
ls -1 "${DSH_HOME:-$HOME/.dsh}/profiles" | grep -v '^node_modules$'. - Add the pinned version with
dsh plugin --profile <profile> add [email protected]. (inferred, check the README) - Verify with
dsh plugin --profile <profile> list --depth 0, checking that DSH Plugin Shop is in the output. (inferred, check the README) - Restart the profile with
dsh --profile <profile>. (inferred, check the README)
Prompt for your agent
For the LivXue/dsh-plugin-shop repo, list the profiles in ${DSH_HOME:-$HOME/.dsh}/profiles, then run `dsh plugin --profile <profile> add [email protected]`. Expect a list output from `dsh plugin --profile <profile> list --depth 0` that includes dsh-plugin-shop, and also check that dsh.profile.bundles in <profile>/package.json includes the plugin.
Caveat. The README says exit code 0 only means pnpm resolved the package, so the list check is required to confirm the plugin is really installed.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page