DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to add a community bundle to a DSH web profile with Awesome DeepSeek Harness

Install an external profile bundle with dsh plugin and activate it on the web profile.

Remote script. Installing a bundle from GitHub runs third-party code on your machine, so read the package source before you add it.

Who it is forA DSH user who found a bundle in the list and wants its layers active in the web profile.

The problemPlain package installs stay inactive, so it is not obvious how to turn a bundle on.

The outcomeThe bundle is installed and active in the web profile after you restart DSH.

What you need first

  • Node.js installed, for the npx command that starts the official DSH web runtime
  • pnpm on your PATH, for installing external profile bundles with dsh plugin
  • A project folder or Git repository where the agents can work
  • Review of each third-party plugin's source before installing it

Steps

  1. Pick a bundle from the list and note its GitHub owner, repo, and ref.
  2. Run dsh plugin --profile web add "github:owner/repo#ref" with your values.
  3. Confirm the package declares dsh.bundle.patch, since only those become active profile layers.
  4. Restart with dsh --profile web.

Prompt for your agent

Using the repo 0xsline/awesome-deepseek-harness, install the bundle at <github owner/repo#ref> with `dsh plugin --profile web add "github:<owner/repo>#<ref>"`. Report the install output and whether the package declares dsh.bundle.patch. Verify by restarting with `dsh --profile web` and checking the bundle appears in Settings → Plugins.

Caveat. The README says the older sub-path and Repository Plugin install forms are no longer part of the official flow, so use only packages that declare dsh.bundle.patch.

Share: 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