arkyu2077/awesome-dsh-plugin
面向 DeepSeek Harness 用户的插件产品说明书与导航:按场景选插件,了解安装、权限、兼容性和风险
项目介绍Project Overview
DSH 插件生态社区目录,托管于 dshplugin.dev。它汇总 1,488 条插件记录,提供 87 项公开基线(已发布 87、候选 1166、隔离 216、驳回 19),覆盖开发工具、自动化、浏览器交互、界面设计、会话管理、模型集成、安全控制与存储等类别,并按用途、许可、权限与维护情况提供审核清单。适用于快速定位、安装前核查及故障排查。注意:目录独立于 DeepSeek,上架不等同推荐或安全认证,浏览时需自行核实当前状态。
Awesome DSH Plugin is a community directory and user handbook for the DeepSeek Harness plugin ecosystem, hosted at dshplugin.dev. It catalogs 1,488 records and exposes an 87-page public baseline across categories such as developer tools, automation, browser interaction, interface design, session management, model integrations, security, and storage, with guidance on permissions, maintenance, and installation verification. Use it to compare plugins, inspect access scope, and troubleshoot compatibility issues. The directory is independent from DeepSeek, and a listing is not a recommendation, security audit, or compatibility certificate.
请帮我了解并安装插件:【awesome-dsh-plugin】【https://github.com/arkyu2077/awesome-dsh-plugin】
把上面这条消息直接发给当前会话里的 DSH,让它帮你了解并安装。安装命令不一定准确,发给 DSH 更稳。Send this message to DSH in your current session. CLI install commands may not be accurate across systems — DSH will figure it out for you.
或使用命令行安装(适合开发者)Or use CLI install (for developers)
命令行安装CLI Install
dsh plugin --profile web add github:arkyu2077/awesome-dsh-plugin
把 arkyu2077/awesome-dsh-plugin 加入你的 DSH 配置(web profile)即可启用。
READMEREADME
Awesome DSH Plugin
A user handbook and plugin navigator for DeepSeek Harness.
English · 简体中文 · 日本語 · Español
Understand what a plugin does and what access it needs, then open its complete page on dshplugin.dev. You can also click the logo above to visit the website.
What this handbook is for
DeepSeek Harness, or DSH, follows an “Everything is a Plugin” model. Community plugins can add development tools, automation, browser interaction, interface design, session management, model integrations, security controls, and storage.
This repository is written for people who want to use those products. It is not an API reference, architecture guide, or plugin-development manual. It helps you answer four practical questions:
- Which kind of plugin matches my goal?
- What should I inspect before installation?
- Where can I find the latest plugin information?
- What should I do when permissions or compatibility cause problems?
Every published plugin name opens an internal dshplugin.dev detail page. The repository also keeps the complete 1,488-record discovery snapshot visible, including candidates and records withheld from publication. Only the 87-page public baseline verified on 2026-08-17 receives a detail-page link, so visibility is never confused with publication or recommendation.
[!IMPORTANT]
dshplugin.devis an independent community directory. It is not an official DeepSeek website, and a listing is not an endorsement by DeepSeek or the publisher. A public repository, star count, or recent update does not prove safety, compatibility, or maintenance quality.
Start here
| What you want to do | Recommended page |
|---|---|
| Search by plugin name or use case | Complete plugin directory |
| Install a DSH plugin for the first time | Installation and verification guide |
| See projects newly admitted to the public catalog | New releases |
| Find projects with recent source updates | Recently updated |
| Use GitHub stars as an initial signal | Most starred |
| Browse the work of an author or team | Publisher directory |
| Understand inclusion and correction rules | Editorial policy |
| Review ecosystem size and category trends | Ecosystem report |
Complete ecosystem inventory
Nothing in the 2026-08-17 snapshot is hidden. Open the complete inventory to browse all 1,488 records by publication status:
| Inventory | Records | What you can do |
|---|---|---|
| Published | 87 | Open the plugin's complete product page on dshplugin.dev. |
| Candidate | 1,166 | Review the name, category, summary, language, and license while human publication review is pending. |
| Quarantined | 216 | See records kept for audit because the available evidence is incomplete. |
| Rejected | 19 | See records that failed a hard publication gate. |
Candidate, quarantined, and rejected names are deliberately not linked to individual website pages because they are not part of the controlled public baseline. Some transitional URLs may still resolve while website cleanup is in progress. This keeps the full collected inventory visible without treating unstable pages as published destinations.
Choose by use case
The category files below are the clickable 87-page public catalog. The complete inventory separately exposes all 1,488 collected records without treating every discovery as published.
| Category | Use it when you need | Snapshot | Complete catalog |
|---|---|---|---|
| Developer Tools | Code, terminal, file, debugging, API, or local-workflow improvements | 46 | Browse baseline |
| Automation | Repeatable tasks, agent coordination, orchestration, or integrations | 10 | Browse baseline |
| Browser | Navigation, research, extraction, testing, or browser bridges | 9 | Browse baseline |
| UI & Design | Interfaces, themes, visualization, design, or preview workflows | 6 | Browse baseline |
| Models | Model adapters, routing, fallback, or inference providers | 2 | Browse baseline |
| Sessions | History, memory, context, summaries, or conversation workflows | 9 | Browse baseline |
| Security | Permissions, sandboxing, policy, secrets, or defensive controls | 5 | Browse baseline |
| Storage | Persistence, databases, caches, or artifact storage | 0 | Baseline status |
How publication status works
Discovery and publication are separate decisions. Automated crawling can identify a project, but it cannot promote that project into this public catalog.
| Status | What it means for users |
|---|---|
| Public baseline | The historical cohort verified as indexed in Search Console. It is linked here to preserve stable URLs, but this does not prove a fresh manual review or safety certification. |
| Candidate | Passed initial automated checks and is waiting for human review. It is visible in the complete inventory but has no detail-page link. |
| Quarantined | Evidence is incomplete or does not yet establish a substantive DSH plugin. It is visible for audit but remains outside the public catalog. |
| Rejected | Archived, inaccessible, empty, or otherwise failed a hard gate. It remains visible in the audit inventory but should not be revived by a later crawl. |
The wider ecosystem report can contain discovery and audit totals that are larger than this catalog. That difference is intentional: quality and stable indexation take priority over publishing every discovered repository.
Live website categories:
A safer way to use community plugins
1. Run the base Harness first
For a first run, start the official Web UI with:
npx @deepseek-ai/dsh web
The documented default address is http://127.0.0.1:3080. Confirm that the base product works before adding third-party code. This gives you a clean baseline when something later fails.
2. Review the website detail page
Before installing, check:
- whether the plugin solves the problem you actually have;
- whether the complete install command comes from current publisher documentation;
- the intended profile, DSH version, operating system, and prerequisites;
- the latest update, open issues, and maintenance notes;
- whether the license fits personal, team, or commercial use;
- external services, accounts, secrets, or paid APIs it requires;
- screenshots, demos, or reproducible output supporting its claims.
3. Inspect permissions before granting them
A plugin is third-party code. Pause and read the source and publisher explanation if it can:
- read or write local files, or execute terminal commands;
- control a browser, inspect pages, or use an authenticated session;
- access the network, upload content, or call external APIs;
- read environment variables, credentials, sessions, or chat history;
- change model routing, approval policy, or security settings.
If a detail page has no install command or permission explanation, treat it as informational. Do not invent a command from the repository name.
4. Verify one capability at a time
- Keep the publisher's profile, branch, tag, and version information intact.
- Refresh or restart the intended profile and check for load or approval errors.
- Run the smallest reversible example in the documentation.
- Grant only the permissions the advertised capability needs.
- Record the repository and installed revision so you can reproduce or reverse the change.
How to compare two plugins
Do not use star count alone.
| Dimension | Question to ask |
|---|---|
| Need fit | Does the plugin solve your exact problem, or does it only mention DSH? |
| Installation clarity | Does it provide a complete command, target profile, and prerequisites? |
| Compatibility | Does it name supported DSH versions, systems, and known limitations? |
| Permission scope | Are requested capabilities proportional to the feature? |
| Verifiable evidence | Is there a screenshot, demo, sample output, or test procedure? |
| Maintenance | Are updates recent, issues answered, and breaking changes documented? |
| License | Can you use it in your personal, team, or commercial setting? |
| Exit path | Can you disable, remove, or roll it back cleanly? |
Troubleshooting
The plugin does not appear after installation
Recheck the profile, package name, branch, or tag. Then inspect the Harness interface and publisher issues for a load error. Avoid installing several new plugins at once, because that makes the failing change harder to isolate.
It stopped working after an update
DeepSeek Harness is still changing quickly, and the official project warns about compatibility-breaking changes. Compare the Harness version, the plugin's last update, and the publisher's compatibility notes. Return to a recorded working version when necessary.
It requests broad access
Stop before approving it. Confirm that each permission is directly connected to the feature, then inspect the source, rationale, and issue history. Unexplained file, browser, network, or secret access should not be granted.
Does a listing mean the plugin is recommended or certified?
No. A listing means the directory found and normalized public-source information. It is not a security audit, compatibility certificate, quality guarantee, or official recommendation.
Data scope and updates
- Snapshot date: 2026-08-17
- Complete discovery snapshot visible in this repository: 1,488 records
- Controlled public baseline in this repository: 87 plugin pages
- Publication review queues: 1,166 candidates, 216 quarantined, and 19 rejected
- Categories represented in the baseline: 7, plus an empty Storage status page
- Sources: public GitHub repositories, npm metadata, and publisher pages
- Live status: Ecosystem report
- Inclusion method: Editorial policy
Plugin names, descriptions, licenses, and activity can change. The complete inventory preserves the audit snapshot; the category files remain the controlled clickable catalog. For a published plugin, use its website detail page and publisher source to verify current status.
Submit or correct a listing
Plugin authors can publish a clear public repository, add the dsh-plugin GitHub topic, and follow the submission guide. Discovery creates a review candidate; it does not automatically publish a listing.
For a correction or missing project, provide public-source evidence through the contact page or a repository issue. See CONTRIBUTING.md for contribution rules.
Independent status
This repository and dshplugin.dev are independent community projects. They are not affiliated with DeepSeek and are not endorsed by DeepSeek or any listed publisher. DeepSeek, DeepSeek Harness, plugin names, logos, and trademarks belong to their respective owners.
freestylefly/awesome-gpt-image-2
awesome-dsh-plugin/awesome-dsh-plugin
dsh-market/dsh-market
AdamPlatin123/awesome-dsh-plugins
Anil-matcha/awesome-dsh-plugin
0xsline/awesome-deepseek-harness
superdesigndev/treg