DSH HUB
HomePlugin StorePlugin PacksCommunityRankingsResourcesPublish Guide
Plugin source
Back to catalog

youyou-sudo /

youyou-sudo/dsh-plugins

Topic repository only

youyou-sudo's personal DSH plugin market: small, dependency-free DeepSeek Harness bundles installable straight from Git, with a generated format-1 market index on GitHub Pages.

★ 0 Stars0 Forks0 IssuesN/A Community rating0 Confirmed installs
View on GitHubProject homepage
READMESource: main@759b8d69

Youyou's DSH plugins

Personal DeepSeek Harness (DSH) plugin market: ten curated upstream plugins installed from their official npm packages or pinned upstream Git commits. The repository also keeps the contract for publishing your own plugin from its plugins/ directory.

  • Market index (subscribe URL): https://youyou-sudo.github.io/dsh-plugins/index.json
  • Market site: https://youyou-sudo.github.io/dsh-plugins/
  • Inspiration: klarkxy/dsh-plugins
  • DSH repository: deepseek-ai/deepseek-harness

Like the repository that inspired it, this one does not publish to npm: a plugin published from this Git repository would be installed directly from the repository at a tagged, commit-pinned version, and the market index index.json is generated by a script and published with GitHub Pages. The index currently lists only curated upstream plugins (site/curated.json), whose source code is not redistributed here. The market tooling is dependency-free and runs on Bun >= 1.2: Bun executes the TypeScript scripts directly, so generating the index and the site has no build step. A plugin published here is the exception: its TypeScript source is built to a Node-compatible ESM entry because DSH's own host runs on Node (see plugins/AGENTS.md).

Contents

  • Subscribe to this index
  • Plugins
  • Install without the market
  • Repository layout
  • Adding a plugin
  • How the index is generated and published
  • Local verification
  • Security notes
  • License

Subscribe to this index

  1. Open the Plugins page in the Web sidebar and enable Custom plugin indexes (the @deepseek-ai/dsh-experimental-plugin-market-bundle bundle) under Experimental plugins. A Discover tab appears.
  2. Open Discover, click Add index source, paste https://youyou-sudo.github.io/dsh-plugins/index.json, and confirm.
  3. Pick a plugin from the list and install it. Every version is pinned — an exact npm version, or a commit for Git-sourced plugins — and the entry page shows the exact install arguments.

You can also configure the indexes option of the plugin-market row in a profile directly (an array of canonical http: or https: URLs in display order, without credentials or fragments):

# Example fragment for the plugin-market row in a profile; use your profile's real structure.
config:
  indexes:
    - https://youyou-sudo.github.io/dsh-plugins/index.json

Adding a source from the Discover UI is simpler; profile configuration is useful for setting up environments by script.

Plugins

The market index can list two classes of plugins in one index:

  • Curated upstream (site/curated.json, the only class listed today) are third-party plugins worth keeping in one place. This repository does not redistribute their code: every entry points at the upstream npm package (or pinned upstream Git commit) and keeps its upstream repository, homepage and license.
  • Published here (plugins/, currently none) are maintained in this repository, tagged and installed as commit-pinned Git versions. The directory stays as the place where future locally published plugins live.

Curated upstream plugins

Plugin Title Upstream source Latest version License
@klarkxy/dsh-git-commit Git Commit npm 0.3.3 SEE LICENSE IN LICENSE
@klarkxy/dsh-current-title Auto Title npm 0.3.3 SEE LICENSE IN LICENSE
@klarkxy/dsh-delegation Delegation Mode npm 0.1.3 SEE LICENSE IN LICENSE
@klarkxy/dsh-unrestricted Unrestricted npm 0.3.1 SEE LICENSE IN LICENSE
@klarkxy/dsh-dev-index DSH Docs npm 0.2.9 SEE LICENSE IN LICENSE
dsh-plugin-save-token Save Token npm 2.4.1 MIT
dsh-ops Ops npm 0.5.0 MIT
dsh-context Context Dashboard npm 0.83.0 Apache-2.0
dsh-doyourweb Web Control npm 0.2.2 MIT
dsh-away-notify Away Notify Git commit 0.1.0 MIT

Titles, descriptions, licenses and upstream links come from site/curated.json; the generated site shows the full entry for each plugin. When an upstream package declares no DSH range, the entry uses engines.dsh "*" (compatible with any DSH version). Updating a curated entry means editing site/curated.json and regenerating index.json — there are no tags for upstream releases. Read the upstream repository and license before installing; these plugins are not security-reviewed here.

Publishing a plugin from this repository

No plugins are published from this repository at the moment. The plugins/ directory and its contract (plugins/AGENTS.md) stay in place: to publish your own plugin here, put the package under plugins/<dir>/, build its Node-target entry, add a site/catalog.json entry, tag <dir>@<version>, and regenerate the index (see Adding a plugin). The tagged plugin then appears in the index next to the curated entries, installed from this Git repository at the tagged commit.

Install without the market

For a curated upstream plugin, copy its install spec from index.json or bun run scripts/build-index.ts --specs: an npm source installs as <name>@<version>, and a Git source installs as git+<upstream repository>.git#<commit> (plus &path:/<directory> when the package sits in a subdirectory of that repository). For example:

dsh plugin --profile <profile> add "@klarkxy/dsh-git-commit@0.3.3"
dsh plugin --profile <profile> add "git+https://github.com/s11phere/dsh-away-notify.git#8d6e67389975f3c849cd0eb0722317e33599f8a9"
  • <profile> is your DSH profile name.
  • The arguments are exactly what the market's Install button produces; pass them to dsh plugin add unchanged.
  • bun run scripts/build-index.ts --specs prints every version's name and install spec in one go. A future plugin published from this repository would be installed as git+https://github.com/youyou-sudo/dsh-plugins.git#<commit>&path:/plugins/<dir>.

Repository layout

.
├── index.json              # generated market index (format 1), published with Pages
├── package.json            # Bun scripts and engines.bun >= 1.2
├── tsconfig.json           # TypeScript configuration (Bun runs the sources directly)
├── plugins/                # plugins published here; none at present
│   └── AGENTS.md           # bundle contract for future plugin authors
├── site/
│   ├── catalog.json        # market metadata, categories and order; `plugins` is currently empty
│   ├── curated.json        # curated upstream plugins (npm or upstream git, no redistribution)
│   ├── curated-icons/      # icons for curated entries, copied to _site/icons/
│   ├── build.ts            # generates the static site in _site/
│   └── render.ts           # pure render functions
├── scripts/
│   ├── build-index.ts      # builds index.json from catalog, curated list, package.json and git tags
│   ├── validate-index.ts   # validates index.json against format 1
│   ├── check-index.ts      # checks the index against this repository (CI / Pages)
│   └── lib/                # TypeScript libraries: versions, git, catalog, curated, index format, install specs
├── tests/                  # bun:test tests and fixtures
├── .github/workflows/      # ci.yml, pages.yml
├── AGENTS.md               # contracts and verification checklist for future agents
├── RELEASING.md            # release process
└── README.md               # this file

Adding a plugin

  1. Create plugins/<dir>/ following the bundle contract in plugins/AGENTS.md: package.json, cordis.patch.yml, TypeScript sources under src/, the Node-target lib/index.js built from them with bun build --target=node, icon.svg, README.md, README.zh-CN.md, test/*.test.ts.
  2. Add an entry to site/catalog.json with directory, title, description (both languages), category (a declared category), labels, and order.
  3. Set the version in plugins/<dir>/package.json to a new exact SemVer version (for example 0.1.0).
  4. Commit, then tag: git tag <dir>@<version> (for example your-plugin@0.1.0; no v prefix).
  5. Run bun run scripts/build-index.ts and commit the regenerated index.json (plus the site/catalog.json change).
  6. Push main and the tags; the Pages workflow revalidates the index and redeploys the site.

Never reuse or move a published tag; old versions stay installable because they pin commits. See RELEASING.md for the full process and rollback notes.

Adding a curated upstream plugin

  1. Add an entry to site/curated.json: name (the upstream npm package name), title/description (both languages), category (declared in site/catalog.json), order (display order, after the existing curated entries), repository, the upstream dist-tags.latest and versions (source is { "type": "npm" } or a pinned upstream git commit), plus engines.dsh ("*" when the upstream package declares none).
  2. Optionally add an icon under site/curated-icons/ and reference it as site/curated-icons/<file> in the entry.
  3. Run bun run scripts/build-index.ts, commit site/curated.json, the icon, and the regenerated index.json.
  4. Re-run bun test, bun run scripts/validate-index.ts and bun run scripts/check-index.ts.

Curated entries are display metadata only: the install spec points at the upstream npm version or the pinned upstream commit, so this repository never redistributes the code.

How the index is generated and published

  • Inputs: site/catalog.json (title, description, category, order; plugins may be empty), plugins/<dir>/package.json for every cataloged local plugin (name, version, engines.dsh, keywords), git tags named <dir>@<version> (commit and commit date), and the optional site/curated.json curated upstream list (npm or upstream git versions).
  • bun run scripts/build-index.ts writes index.json (format 1, two-space JSON with a trailing newline). When the current package.json version of a local plugin has no tag yet, it also emits a version pinned to HEAD. Local and curated entries are merged into one plugins array sorted by order ascending, ties broken by plugin id; curated entries emit only format-1 members (license and other curated-only fields stay in site/curated.json).
  • index.json is committed to the repository. On every push to main, pages.yml runs bun run scripts/check-index.ts, then bun run site/build.ts --out _site, and publishes _site/, which contains a byte-for-byte copy of index.json, the icons, and the site pages.
  • The format rules are summarised in AGENTS.md; DSH reads and validates indexes with its @deepseek-ai/dsh-plugin-market-index package.

Local verification

bun test                                       # all tests (repository; plugin tests when plugins exist)
bun run scripts/build-index.ts                 # generate index.json (needs a git repository and tags)
bun run scripts/validate-index.ts              # validate index.json
bun run scripts/check-index.ts                 # check the index against local git history and tags
bun run site/build.ts --out _site              # build the site locally (_site/ is gitignored)
bun run scripts/build-index.ts --specs         # print every version's name and install spec
bun run scripts/build-index.ts --check         # CI: exits 1 when index.json is stale

bun test auto-discovers every *.test.ts from the repository root, including any tests under plugins/. bun test tests/versions.test.ts runs a single file. _site/ is generated output and must not be committed.

Security notes

  • Market content is third-party content; this index is yours, but still install plugins only from sources you trust. Curated upstream entries are not reviewed or redistributed here: each one points at its official npm package or upstream git commit, and its license stays with the upstream author.
  • The index is not signed: index.json declares names, versions, commits and similar metadata; what actually gets installed is determined by the installed manifest. Each version is pinned to an exact npm version or commit, so a given version cannot be silently replaced.
  • Do not delete or move pushed tags, and do not rewrite the history of main; already-installed pinned commits keep working, but index validation will fail.
  • Use HTTPS for the index; http is fine for local development, but do not configure untrusted URLs in a production profile.
  • Plugins are host plugins that run inside your DSH profile: read the source before installing.
  • This repository stays dependency-free (Bun built-ins only, no npm packages) to keep the supply chain small.

License

MIT (2026 youyou-sudo).

—/ 5

No ratings yet

Manifest verification required

Commit 759b8d697c07

Community comments

No comments yet. Be the first to write one.

DSH HUB

A community index for DSH plugins. Not an official GitHub or DeepSeek AI product.

CommunityResourcesAPIAbout