DSH Quick Start: From Install to Your First Verified Plugin
Go from zero to a verified plugin in ten minutes: install the DSH CLI, pick from the plugin registry, and read the L1-L5 verification badges like a pro.
DSH (DeepSeek Harness) is DeepSeek AI’s open-source agent harness — an everything-is-a-plugin architecture powered by Cordis. This tutorial walks you through ten minutes from zero: install the CLI, pick a plugin, and install your first verified one.
Step 1: Install the DSH CLI
The DSH CLI is published on npm:
npm install -g @deepseek-ai/dshVerify that the dsh command works in your terminal (version requirements and install options: see the official repository README).
Step 2: Pick a plugin from the registry
Don’t install blind. Every plugin differs in capability, security posture, and verification level. Browse the dsh.so registry and filter by use case — GitHub integration, web search, terminal, vision/OCR, databases, notifications. Every entry is verified to exist via the GitHub API and automatically security-scanned.
Two badges matter when picking:
| Badge | Meaning |
|---|---|
| Security | Automated scan risk level — informational, not a substitute for your judgment |
| Verification | L1 Found → L5 Run tested; higher means we actually tested deeper |
Step 3: Install the plugin
Each plugin’s detail page has a copy-paste install command. The basic form:
dsh plugin add <plugin>For plugins that run inside the dsh web UI, use the web profile:
dsh plugin --profile web add <plugin>How to read the verification ladder
dsh.so runs every listing through a five-level ladder (details: Verification):
- L1 Found — the repository exists, is non-empty, and has a README;
- L2 Structured / L3 Install spec — metadata is complete and an install method can be derived reliably;
- L4 Install tested — installed for real inside an isolated sandbox;
- L5 Run tested — the sandbox boots dsh web with the plugin loaded and passes smoke checks.
L4/L5 only count real verdicts on the current dsh version — after an upgrade, older results expire automatically and get re-tested. A “verified” badge means it truly installs on the version you’re running today.
Next steps
- Write your own plugin: follow the plugin development guide, chapter by chapter through the official Cordis tutorial;
- Published a plugin? Submit it — listings enter the security-scan and install-verification pipeline automatically;
- Need a model API key for your plugins? Start from the free tiers in our token resources roundup (Chinese edition) at AI Token 免费资源汇总.
If a plugin won’t install, check its verification record on the detail page to locate the failure; if the registry data itself is wrong, please report it.