DeepSeek Harness Plugin Hub

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

探索

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

社区

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

相关链接

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

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

DeepSeek Harness Plugin Hub
ProfilesPlugins分类动态文档登录管理 Profiles
ProfilesPlugins分类动态文档登录
← Plugins
A

@liangminhua/agent-notes-toolkit

Agent Notes Toolkit

便携式 Agent Notes 机制:验证门、脚手架 CLI、维护技能以及适用于 dsh 的 AN 预设

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

npx -y @deepseek-ai/dsh plugin --profile web add github:liangminhua/agent-notes-toolkit#2b95b34e3948d83be7b8bca2c9e669953cf2e0f8
README兼容性版本

兼容性与来源证明

Agent Notes Toolkit 以 @liangminhua/agent-notes-toolkit 发布,当前版本为 0.1.0。Plugin Hub 会校验它的 manifest,并保存精确安装来源,便于复现安装结果。

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

版本

0.1.0stable
2026/9/2

相关插件

正在加载相关插件…

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

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

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

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

认领这个 Plugin →
报告问题

相关插件

继续浏览 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 传输 / 本地端口转发隧道 / 集群执行Opsdsh-ops适用于 Windows x64、Linux x64 和 macOS arm64/x64 的原生文件和 PTC 工具;仅限 Windows 的可选 Bash 负载和主机 PowerShell 集成Update@linxin666/dsh-update用于 dsh Web GUI 的自更新插件:探测 npm 上是否有更新的系列版本,并在原地运行所属配置的 pnpm 更新;可通过设置图标旁侧边栏中的触发器启动,并显示发布说明面板

README

Agent Notes Toolkit (AN)

English | 中文

The portable Agent Notes mechanism: a decision-record tree, verification gates, a scaffolding CLI, maintenance skills, and the AN preset for dsh.

Install

One-off use needs no install — npx runs the current version directly:

npx --yes @liangminhua/agent-notes-toolkit an verify   # run once, nothing installed

The --yes form skips the install prompt; the package downloads into the npx cache and is never added to your project. Install it as a devDependency only when a project pins the toolkit version (CI, npm run scripts, repeated local use):

npm install --save-dev @liangminhua/agent-notes-toolkit

Both forms run the identical engine; CI should use the pinned devDependency form (npm exec an verify) so a version bump cannot change what the pipeline runs.

Use

npx an init          # scaffold the .agents/notes skeleton + seed note + version pin
npx an verify        # run every gate; exit 1 with one violation per line on failure
npx an ci-setup      # detect the CI vendor and write a standalone workflow file (never overwrites)
npx an migrate       # re-scaffold skeleton files to match the toolkit version; note content untouched
npx skills add <owner/repo or git repo>  # copy skills into .agents/skills (skills.sh syntax)
npx an preset-install  # write the AN preset into $DSH_HOME/.agent-presets/an

an verify runs six gates: tree (closed lifecycle/class tree), classification (legacy paths), format (header block + skeleton + alternatives), archive (frozen archive seals), links (relative links and anchors), and wrap (one physical line per paragraph). GitHub gets .github/workflows/agent-notes.yml; GitLab gets a standalone .gitlab/agent-notes.yml include file with the include line printed.

dsh integration

dsh plugin --profile web add github:liangminhua/agent-notes-toolkit   # bundle from GitHub, no npm publish
an preset-install                      # the AN mode appears in the preset picker

The package declares dsh.bundle.patch, so the publish guide's GitHub install form resolves the bundle from the repository root. AN mode is an isolated agent preset, separate from standard/ptc/cordis: only its sessions get the notes-verify model tool and the AN skills (skills arrive through the tool plugin's runtime registrations — one delivery channel, no second one). The model tool, the commands, and the CLI share one engine (lib/engine.js): in-session tool calls and CI execute the same gate code. The bundle is self-contained (vendor sync + drift guard) and does not depend on the toolkit being installed.

Release status

npm publish passes dry-run and publishConfig.access is public. The real publish needs one 2FA code per package (registry policy): run npm publish --registry https://registry.npmjs.org in the repository root, then again in packages/dsh-an/, entering the code each time. The GitHub repository itself (including the git-dependency install path) is usable today.

Contract

See SPEC.md and the Agent Note rules (scaffolded into your project by an init). Every gate and CLI shares one engine; exit code 0/1 is the CI enforcement language.

Development

npm install
npm test        # node:test full suite
npm run verify  # self-hosted: this repository runs its own gates