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

dsh-pwsh-guard

Pwsh Guard

DSH (DeepSeek Harness) 插件:拒绝在 pwsh/bash/ops_bash 中使用 shell 文本 I/O——Select-String、Get-Content、findstr、rg、cat、node -e——并引导代理使用 read/grep/glob。

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

npx -y @deepseek-ai/dsh plugin --profile web add dsh-pwsh-guard@0.3.1
README兼容性版本

兼容性与来源证明

Pwsh Guard 以 dsh-pwsh-guard 发布,当前版本为 0.3.1。Plugin Hub 会校验它的 manifest,并保存精确安装来源,便于复现安装结果。

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

版本

0.3.1stable
2026/10/29
0.3.0stable
2026/10/29
0.1.0stable
2026/10/20
查看其余 1 个版本收起版本
0.2.0stable
2026/10/20

相关插件

正在加载相关插件…

最新版
0.3.1
DSH
*
HMR
重启进程
Tree shaking
未声明可安全裁剪
解包体积
32.8 kB
文件数
12
Surface
any
许可证
MIT
发布源
npm
GitHub
★ 0
周下载
485
安全扫描
✓ v0.3.1 扫描通过
最近提交
2026/10/29
查看源码 ↗项目主页 ↗
README Badge

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

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

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

认领这个 Plugin →
报告问题

相关插件

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

Web App@deepseek-ai/dsh-web-appdsh 浏览器界面捆绑包:位于 dsh-base 之上的 Web 补丁层,加上运行时粘合插件(提供前端 dist、Web 界面提示符、bash 运行时变量和 URL 行)Sdk Minimal@deepseek-ai/dsh-sdk-minimal独立的最小 SDK 配置包:JSON-RPC、一个 DeepSeek 适配器、持久化 Shell 和 JSONL 会话Sdk App@deepseek-ai/dsh-sdk-appdsh SDK 配置包:基于 dsh-base 提供 stdio JSON-RPC 服务和进程生命周期管理Experimental Inspector@deepseek-ai/dsh-experimental-inspector用于 Host 调试和 Client Runtime 检查的实验性跨 realm CDP hub

README

dsh-pwsh-guard

English | 简体中文

A DeepSeek Harness plugin that enforces one rule: read files with read, search with grep, locate files with glob — not with shell text commands.

It registers a ctx.tools.guard over pwsh, bash and ops_bash. A call whose command line performs file text I/O is rejected before execution, and the rejection reason names the tool to use instead. Rejection messages follow the host locale (English or Chinese).

Rules

idgroupblocksuse instead
search.Select-String, search.slstextSearchSelect-String, slsgrep
search.findstr, search.grep, search.rgtextSearchfindstr, grep, rggrep
read.Get-Content, read.gc, read.cat, read.typetextReadGet-Content and its aliasesread
read.more, read.head, read.tailtextReadmore, head, tailread
bypass.node-eval, bypass.python-c, bypass.php-r, bypass.dotnet-ioruntimeBypassnode -e, python -c, php -r, [IO.File]::ReadAllText that read filesread, grep
wait.Start-Sleep, wait.sleepsleepStart-Sleep, sleepprobe the port, read the job again later, schedule_create
pipeline.stderr-mergestderrMerge2>&1 followed by a pipe$LASTEXITCODE, 2>err.txt
job.waitjobWaitjob_output called with wait: trueprobe the port (Test-NetConnection, curl), or read the job again later

Two matching rules keep false positives down:

  • Short aliases match in command position only (^, ;, |, &, (, {, $(), so Get-ChildItem -Type f, git gc and git log --grep=x pass.
  • Quoted spans are ignored, so git commit -m "stop using Select-String" passes. Rules that inspect a script body (node -e ...) read the raw string.

Configuration

All fields are optional.

- id: pwsh-guard
  name: 'dsh-pwsh-guard'
  config:
    enabled: true
    language: auto          # zh | en | auto
    tools: [pwsh, bash, ops_bash]
    disabledGroups: []      # textSearch | textRead | runtimeBypass | sleep | stderrMerge | jobWait
    allowPatterns: []       # regexes matched against the raw command; a match allows the call
    rules: []               # extra rules, evaluated before the built-ins

language: auto follows DSH_LOCALE, then the host locale, then LANG / LC_ALL.

    rules:
      - id: no-force-push
        pattern: 'git\s+push\s+--force'
        title: 'Force push is blocked'
        hint: 'Use --force-with-lease instead'

Installation

From npm:

plugin_manager action: install_bundle target: dsh-pwsh-guard

From GitHub:

plugin_manager action: install_bundle target: https://github.com/Steven-Qiang/dsh-pwsh-guard

From a local checkout (link:, for development):

git clone https://github.com/Steven-Qiang/dsh-pwsh-guard
plugin_manager action: install_bundle target: /path/to/dsh-pwsh-guard

After editing code or config, reload without restarting:

plugin_manager action: set_plugin target: include:pwsh-guard enabled: false
plugin_manager action: set_plugin target: include:pwsh-guard enabled: true

Uninstall: plugin_manager action: remove_bundle target: dsh-pwsh-guard.

If install_bundle reports failedAt: registry, the failure came from another dependency of the profile; the package link, package.json entry and cordis.yml row are usually already written. Check for node_modules/dsh-pwsh-guard/index.js and the id: pwsh-guard row before retrying.

Limitations

  • Command names inside quotes (& "Select-String", powershell -Command "Get-Content x") are not detected.
  • -EncodedCommand is not decoded.
  • ops_bash --script_path is checked by path only, not by script content.
  • Directory listing (Get-ChildItem, ls, dir) is out of scope.
  • Not a sandbox. For destructive commands and secret access use a dedicated guard such as cc-safety-net; its rule schema cannot express "deny every use of this command", which is why this plugin exists.

Development

npm test

Builds with tsdown, then runs 36 command fixtures and 11 configuration assertions.

Release

Versions are owned by CI — do not edit version. Pushing to main runs .github/workflows/release.yml:

commitsbump
fix:patch
feat:minor
feat!: or BREAKING CHANGE:major
anything elseno release

Publishing uses npm Trusted Publishing over OIDC, so no NPM_TOKEN is stored. It requires permissions.id-token: write (configured), Node ≥ 22.14 with npm CLI ≥ 11.5.1 (the workflow uses Node 24 plus npm install -g npm@latest), and a repository.url that matches this repository.

The Trusted Publisher is configured on npmjs.com for Steven-Qiang / dsh-pwsh-guard / release.yml. A new package has to be published manually once before that configuration exists, and a new Trusted Publisher must complete a successful publish within 2 days or it expires.