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

How to write a plugin for the everything-is-a-plugin harness with DeepSeek Harness

Build a plugin on the harness architecture and publish it with the dsh-plugin topic.

Who it is forA developer who wants to add a capability to DeepSeek Harness and share it with other users.

The problemExtending an agent harness usually means forking it, while this one is designed around plugins.

The outcomeA plugin repository that is discoverable through the dsh-plugin GitHub topic.

What you need first

  • Node.js installed
  • A terminal and a web browser
  • pnpm, if running from source
  • Git, if running from source
  • Review of the SAFETY.md safety notice before running the project

Steps

  1. Read the architecture documentation in docs/architecture.md.
  2. Read the development guide in docs/development.md.
  3. Clone the repository, run pnpm install, and run pnpm run build to confirm the base project works.
  4. Create your plugin repository on GitHub and add the dsh-plugin topic to it.

Prompt for your agent

Using docs/architecture.md and docs/development.md in the deepseek-harness repository, draft a plugin in <target folder> that <describe capability>. Run `pnpm run build` in the base repo and report whether the plugin loads without errors.

Caveat. The README does not document a plugin API, so the architecture and development docs are the only source for plugin details.

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