DeepSeek Harness Plugin Hub

发布与管理完整 Harness Profiles,发现适合你的插件。

探索

插件目录环境预设文档中心动态

社区

发布插件联系我们报告问题

相关链接

Plugin Hub GitHubDeepSeek Harness 官方项目系统状态隐私说明
© 2026 DeepSeek Harness Plugin HubPowered byPaxTech

独立、非官方社区项目,与 DeepSeek 官方无隶属、授权或背书关系。

Ponytail Sync — DeepSeek Harness 插件(DSH Plugin)
← Plugins
P

dsh-ponytail-sync

Ponytail Sync

Ponytail 懒散资深开发者模式,作为原生 DeepSeek Harness 技能、系统提示词部分和六个斜杠命令提供。始终可用,可切换级别,无需外部进程。

插件会安装到这里;不确定时保持 web。

npx -y @deepseek-ai/dsh plugin --profile web add github:mirelconstantin/dsh-ponytail-sync#ea194c525a714b9a784f169fa279dc100c5c5cd6
README兼容性版本

兼容性与来源证明

Ponytail Sync 以 dsh-ponytail-sync 发布,当前版本为 1.0.0。Plugin Hub 会校验它的 manifest,并保存精确安装来源,便于复现安装结果。

DSH 兼容范围
*
运行环境
any
发布来源
github
Registry 更新时间
2026/10/10

版本

1.0.0stable
2026/10/10

相关插件

正在加载相关插件…

最新版
1.0.0
DSH
*
HMR
重启进程
Tree shaking
未声明可安全裁剪
解包体积
未提供
文件数
未提供
Surface
any
许可证
MIT
发布源
github
GitHub
★ 1
周下载
0
最近提交
2026/10/10
查看源码 ↗
README Badge

点击下方 Badge 复制 Markdown,粘贴到 README 即可。

这是你的 Plugin?认领权益 · 优先安全扫描

验证 package.json 声明的 GitHub 仓库,即可管理这个公开页面。认领后,Hub 会优先安排当前版本的安全扫描,并在通过后公开展示结果。

认领这个 Plugin →
报告问题
DeepSeek Harness Plugin Hub
ProfilesPlugins分类动态文档登录管理 Profiles
ProfilesPlugins分类动态文档登录

相关插件

继续浏览 developer-tools 分类下经过校验的插件。

Client Ui Git Graph@linxin666/dsh-client-ui-git-graph外部 dsh Web GUI 插件:空会话 Git 分支选择器和 Git 图,包含实际的主机端 Git 操作与防护,作为 dsh 配置文件包Ssh@linxin666/dsh-sshdsh Web GUI 的远程 SSH 操作:主机配置存储(~/.dsh/dsh-ssh.json,可从 ~/.ssh/config 导入)、支持跳板主机的持久化 ssh2 连接池、exec / PTY Web 终端 / SFTP 传输 / 本地端口转发隧道 / 集群执行Update@linxin666/dsh-update用于 dsh Web GUI 的自更新插件:探测 npm 上是否有更新的系列版本,并在原地运行所属配置的 pnpm 更新;可通过设置图标旁侧边栏中的触发器启动,并显示发布说明面板Tui@deepseek-harness-tui/dsh-tui用于 DeepSeek Harness 智能体、会话和工具的交互式终端界面。

README

Pazalo

dsh-ponytail-sync

Ponytail lazy-senior-dev mode as a native DeepSeek Harness skill, system-prompt section and six slash commands. Always available, level-switchable, no external process.

Install

From the GUI, paste this into Add plugin:

dsh-ponytail-sync

Or from a terminal:

dsh plugin add dsh-ponytail-sync

That is a plain npm install. It needs neither git nor a GitHub account.

No build step is involved, so nothing needs a build allowlist and every entry point ships as committed source. Restart the profile and four rows appear — the runtime, the skill, the prompt section and the commands.

Other routes
RouteCommand
Pinned to a versiondsh plugin add dsh-ponytail-sync@1.0.0
Pinned to a commitdsh plugin add github:mirelconstantin/dsh-ponytail-sync#<sha>
Tarballdsh plugin add ./dsh-ponytail-sync-1.0.0.tgz
Local checkoutdsh plugin add /absolute/path/to/dsh-ponytail-sync

The GitHub routes need nothing but git access to this repository. The npm route needs neither git nor an account, and is what the command above uses.


What it is

Ponytail by Dietrich Gebert, MIT licensed. It is one instruction prompt plus a handful of one-shot command prompts; everything else in that repository is plumbing that loads the prompt into a particular agent. This bundle ships the prompt into DeepSeek Harness as a skill and as a system-prompt section, so it is present in every session without anyone installing a plugin.

Upstream is the source of truth for the rules. This bundle vendors upstream ponytail 5.1.0 with the review, audit and ledger procedures folded in from the three upstream command skills, and scripts/check-plugin.mjs pins the same ten rule invariants upstream's own scripts/check-rule-copies.js pins — so a silent upstream rule change cannot pass unnoticed.

Why a skill and not an AGENTS.md file

dsh-agent-instructions already loads ~/.dsh/AGENTS.md into every session, and a compact copy of the rules there would work. Three things make the skill the better home:

  • It is loadable on demand. A user-agents copy at rank 500 competes with the per-project file; a runtime registration at rank 250 lets a project's own ponytail skill override it, which is the behaviour a user editing one repository expects.
  • It carries a description that routes it. The catalog shows the description to the model before it loads anything, so the model knows when the mode applies instead of seeing an unconditional block of rules.
  • It is inspectable and editable. assets/ponytail/SKILL.md is one file a maintainer can read and edit; editing it changes what the next session sees after a plugin reload. (The prompt section is not generated from it — the section is deliberately short, and carries the level rather than the rules.)

What it gives a model

A ponytail skill and a ponytail system-prompt section. The section states the active level, what the level changes, and the two lines every reply owes the user. The skill body is the full ruleset with the level tables.

Levels

LevelBehaviour
liteBuild what was asked, name the smaller option in one line
fullThe complete ruleset (default)
ultraAlso question the request before building

The default for new sessions is cordis.patch.yml's ponytail-runtime.config.defaultLevel. A session that changes level keeps that level for the rest of the session, which is what upstream's session-scoped mode does. Changing the default for new sessions is a patch-file edit, not a live Settings row: this bundle ships a plain Standard Schema config, and only a native Schemastery schema renders a Settings form. A plugin must not import @deepseek-ai/schemastery itself, so the row reports unsupported rather than failing the load.

Commands

CommandWhat it does
/ponytail [lite|full|ultra|off]Set the level for this session, or report it with no argument
/ponytail-reviewReview the current change: bugs, security, load, missing tests, speed, what to cut
/ponytail-auditThe same review for the whole repository, ranked
/ponytail-debtHarvest shortcut: comments into a ledger
/ponytail-gainThe measured-impact scoreboard
/ponytail-helpQuick reference card

Files

package.json        the package and its dsh bundle declaration
cordis.patch.yml    the four loader rows
src/index.js        the service entry (provides `ponytail`)
src/config.js       the Config schema, defaults, resolution, level helpers
src/util.js         the config validator and clamping helpers
src/runtime.js      the per-session level and the section text renderer
src/prompt.js       the system-prompt section text and the visibility gate
src/skills.js       the runtime skill registration
src/commands.js     the six slash commands and their one-shot instructions
src/entry-prompt.js the prompt row
src/entry-skill.js  the skill row
src/entry-command.js the command row
assets/ponytail/SKILL.md the vendored ponytail skill body
scripts/check-plugin.mjs  the plugin contract, against a fake context

Enabling it in a profile

The plugin is a bundle: package.json declares dsh.bundle.patch, and the profile lists it in both dependencies and dsh.profile.bundles. dsh plugin add does both edits for you.

// profiles/<name>/package.json
"dependencies": { "dsh-ponytail-sync": "1.0.0" },
"dsh": { "profile": { "bundles": ["@deepseek-ai/dsh-base", "dsh-ponytail-sync"] } }

A checkout can be linked instead, with the bundle name and the directory left as whatever they are:

"dependencies": { "dsh-ponytail-sync": "link:/absolute/path/to/dsh-ponytail-sync" },
"dsh": { "profile": { "bundles": ["@deepseek-ai/dsh-base", "dsh-ponytail-sync"] } }

Then restart DSH once before it resolves. Editing package.json while DSH is running does not make the bundle resolvable: dsh-app-boot's resolveBundleDir probes the node_modules lookup order from the installation anchor and the profile directory, and a running host holds the profile manifest it read at launch. Until the link exists, adding the bundle produces exactly:

dsh: cannot resolve profile bundle "dsh-ponytail-sync" from the dsh installation or <profileDir>;
run 'dsh plugin --profile <name> install' if its dependency is not installed

That install command materialises the link; the restart makes the running host read the new manifest. Do both, then hard-refresh the browser (Ctrl + Shift + R).

To turn the mode off without removing the bundle, set defaultLevel: off in the ponytail-runtime row's config — the skill, the section and the commands stay mounted, and the rules become available on demand through the skill tool.

Verifying it

npm test                    # the plugin contract: levels, section, skills, commands, packaging
node scripts/check-patch.mjs   # the bundle patch, exports and icon match the package
node scripts/check-pack.mjs    # npm would publish every file the plugin needs

The check asserts what a harness does at load time that a hand-mounted test cannot: no default export (the loader unwraps .default in preference to the namespace, which silently drops inject, name and Config and leaves every dependent row pending), that the registrations are effects, that the section suppresses itself when the skill registry is absent or a restriction filtered the skill away, that the level is per session and the budget is actually applied, that all six commands register with a description and a non-empty hint, and that the load-bearing upstream rules survive verbatim in the vendored skill body.

check-pack covers a gap the tests cannot: they run against the repository, while a files entry that stops matching its tree would publish a package that installs and then fails to load.

CI runs the tests and both package checks on Linux and Windows on every push and pull request.

Updating from upstream

Vendor skills/ponytail/SKILL.md into assets/ponytail/SKILL.md, fold in any new upstream command skill you want available, then re-run npm test. It fails when an upstream rule the check pins has moved, which is the prompt to re-read the upstream diff rather than to edit the pinned list.

License

This bundle is MIT — see LICENSE. Ponytail is MIT, © Dietrich Gebert, and is vendored here as instruction text with its attribution and upstream reference intact; NOTICE carries that attribution. icon.svg is the Pazalo mark.