DSH Plugin HubDSH 插件市场
Stormycry-cryp/dsh-AuthInOne 预览 preview

Stormycry-cryp/dsh-AuthInOne

Plugin插件 Native原生 ⭐ 106 MIT Vision & Media视觉与多媒体Usage & Cost用量与计费Models & Routing模型与路由

自包含DeepSeek Harness（DSH）插件，用于Provider/Auth登录、模型切换、图片回退、令牌/成本分析及同端口Web重启。有用的话，点个星支持一下。

Project Overview项目介绍

Edited by Zhiwei Agent (zhiwei)由知微Agent(zhiwei)编辑

dsh-AuthInOne is a native plugin built exclusively for DeepSeek Harness (DSH). It adds support for third-party LLM provider authorization, custom OpenAI-compatible provider configuration, model switching, optional vision fallback for text-only models, token usage analytics, and cost tracking, all integrated directly into DSH’s native Models and Usage settings panels. To install the plugin, users can run the one-line command pnpm dlx github:Stormycry-cryp/dsh-AuthInOne#v0.2.0-alpha.4 install --profile web in their terminal, which handles all setup automatically. This installation process validates the running DSH host, uses the official DSH plugin CLI to add the plugin, and does not require patching DSH core, manual profile edits, or a separate web instance.

This plugin is designed for DSH users who want to add third-party LLM providers like OpenAI Codex and Kimi Code to their DSH instance, or who need to track token usage and associated costs across different models. After installation, users can navigate to DSH’s Settings > Models or Settings > Usage pages to configure new providers, switch default models for future sessions, and view aggregated usage and cost data. OpenAI Codex uses browser OAuth with PKCE and a loopback callback, while Kimi Code uses a device flow that only requires user sign-in and confirmation. Seven providers including xAI Grok, Anthropic, and GitHub Copilot are marked as experimental compatibility, so users should expect potential instability.

The plugin is released under the open-source MIT license, with all third-party dependencies under permissive open-source licenses. The only runtime dependency is Zod, which is also MIT licensed, and build dependencies are bundled so users do not need to install them separately into their DSH profile. For local development, users need Node.js version 22.19 or higher, and can install dependencies with pnpm install --frozen-lockfile to run type checks, tests, and builds. All authorization credentials remain stored locally on the user’s DSH host, and the plugin never reads credentials from other products like OpenCodex. This project is community-maintained and is not affiliated with DeepSeek or OpenAI.

dsh-AuthInOne 是专为 DeepSeek Harness（DSH）开发的原生插件，核心功能包括多 LLM 提供商的登录认证、自定义 OpenAI 兼容提供商配置、模型切换、文本-only 模型可选视觉回退、令牌用量统计和成本追踪，所有功能集成进 DSH 原生的「模型」和「用量」设置面板。该插件当前处于 Alpha 测试版本，适配官方 DSH 指定提交版本，支持通过官方 DSH 插件 CLI 一键安装，无需修改 DSH 核心或手动编辑配置文件。

该插件适合需要在 DSH 中接入 OpenAI Codex、Kimi Code 等第三方 LLM 提供商，或是需要管理自定义 API 密钥、追踪不同模型调用成本的 DSH 用户。部分提供商（如 xAI Grok、Anthropic 等）标注为实验性兼容，用户可按需选择使用。使用时只需执行一键安装命令，安装完成后打开 DSH 设置面板即可开始配置，整个流程无需额外手动操作。

该插件采用 MIT 许可证开源，运行依赖仅为 Zod，开发依赖 Node.js 版本 ^22.19 或 >=24，使用 pnpm 进行包管理，本地开发可通过锁定的依赖文件完成安装、类型检查和测试。所有认证凭证均存储在 DSH 本地，插件不会读取其他产品的凭证信息，当前有七个提供商标注为实验性兼容，不保证所有集成稳定可用。

View on GitHub在 GitHub 查看

Recommended强烈推荐 Send to your DSH发给你的 DSH 安装 
请帮我安装这个 DSH 插件。安装前先完成【兼容性检查 + 安全性检查】，检查通过再动手。

插件：dsh-AuthInOne（Stormycry-cryp/dsh-AuthInOne）
仓库：https://github.com/Stormycry-cryp/dsh-AuthInOne
本站详情页：https://www.yhbd.top/plugins/stormycry-cryp-dsh-authinone/
本站登记：类型 plugin · 归类 原生 DSH 插件 · 许可证 MIT · ⭐ 106 · 最近提交 2026-08-15 · 主语言 JavaScript

按下面顺序执行，每步先把结论告诉我，再进入下一步：

【1 兼容性检查】
① 我这边：DSH 版本、Node 版本、操作系统、当前 profile（web / desktop）。
② 读它的 README、package.json、插件 manifest，列出它要求的 DSH 版本 / Node 版本 / 操作系统 / 外部依赖 / 需要另外先装的运行时。
③ 逐条比对，结论只写「满足 / 不满足 / 未知」三种；不满足的给出可行替代方案。
④ 检查是否和我已装的插件冲突：命令名重复、skill / tool 重名、端口占用、重复注册的 MCP server。

【2 安全性检查】
① 仓库可信度：和上面「本站登记」是否一致；star / fork 数、创建时间、最近提交，是否归档或长期停更。
② 安装脚本：逐行看 package.json 的 preinstall / install / postinstall，以及 install.sh、setup.ps1 之类脚本。出现 curl|bash、下载后直接执行、混淆代码、访问与插件功能无关的域名，立刻停下来告诉我，不要继续装。
③ 依赖：列出新增依赖，标出无人维护、或与知名包拼写近似的可疑包（typosquatting）。
④ 权限与副作用：它会读写哪些目录、访问哪些域名、需要哪些 DSH 权限（filesystem / network / shell / clipboard 等），以及怎么卸载和回滚。
⑤ 如果它要求 sudo / 管理员权限，或权限明显超出功能所需，先停下来问我。

【3 安装】
上面两步没有「不满足」和「高危项」时才执行；用官方推荐方式安装，不要自行提权。

【4 汇报】
用表格输出：检查项 / 结论 / 依据 / 是否需要我决策。拿不准的一律写「未知」并说明要我怎么确认——不要猜，也不要替我决定。

Send this message to DSH in your current session: it verifies compatibility and security first (answering met / not met / unknown item by item) and only installs once everything checks out — it will stop and ask you if it finds a high-risk item. The box scrolls; the copy is the full prompt. CLI install commands may not be accurate across systems, so DSH is the safer route.把上面这条消息直接发给当前会话里的 DSH：它会先核对兼容性与安全性（逐条给「满足 / 不满足 / 未知」），确认没问题再安装，有高危项会停下来问你。框内可滚动，复制到的是完整提示词；安装命令不一定准确，发给 DSH 更稳。

Pre-install check安装前体检Compatibility · Security兼容性 · 安全性 no risk signal found未发现风险信号
  • This site's static screen found no obvious risk signal (stars, license, activity, manifest)本站静态筛查没发现明显风险信号（星标、许可证、更新活跃度、清单完整度）
DSH walks through these 9 checksDSH 会逐条核对这 9 项

Compatibility兼容性

  • DSH, Node, OS and profile requirementsDSH 版本 / Node 版本 / 操作系统 / profile 是否满足要求
  • External dependencies and runtimes (Electron / Python / Docker, ...)外部依赖与运行时（Electron / Python / Docker 等）是否齐备
  • Conflicts with installed plugins: command names, skill / tool names, ports, duplicate MCP registration与已装插件是否冲突：命令名、skill / tool 重名、端口占用、重复 MCP 注册

Security安全性

  • Repo matches the facts registered here; archived or abandoned?仓库是否与页面登记一致，是否归档或长期停更
  • Safety of preinstall / install / postinstall and install.sh / setup.ps1preinstall / install / postinstall 与 install.sh、setup.ps1 是否安全
  • curl|bash, download-then-execute, obfuscation, unrelated domains → stop immediatelycurl|bash、下载即执行、混淆代码、无关域名 → 立刻停止
  • Typosquatting or unmaintained packages among the new dependencies新增依赖里有没有 typosquatting 或无人维护的包
  • Requested permissions vs. what the feature actually needs申请了哪些权限、是否超出功能所需（filesystem / network / shell / clipboard）
  • Any sudo / admin requirement, plus uninstall and rollback是否要求 sudo / 管理员权限，以及卸载与回滚方式

Anything uncertain must be marked unknown with a note on how to confirm it. This site's signal screen is a static snapshot, not a security audit.拿不准的必须标「未知」并说明要我怎么确认。本站的信号筛查是静态快照，不能替代安全审计。

Or use CLI install (for developers)或使用命令行安装（适合开发者）

CLI Install命令行安装 

dsh plugin --profile web add github:Stormycry-cryp/dsh-AuthInOne

把 Stormycry-cryp/dsh-AuthInOne 加入你的 DSH 配置（web profile）即可启用。

READMEREADME

23.7 KB · 缓存于 2026-08-23 03:40:52 · 23.7 KB

dsh-AuthInOne

English | 简体中文

dsh-AuthInOne cover

dsh-AuthInOne is a DeepSeek Harness plugin for Provider login, API and custom OpenAI-compatible Provider setup, model switching, optional vision fallback for text-only models, token usage analytics, and cost tracking inside DSH's native Models and Usage settings.

OpenAI Codex uses browser OAuth with state, S256 PKCE, and a loopback callback. Kimi Code opens the Provider's complete authorization link backed by an RFC 8628 device flow; the link carries the short code, so the user normally only signs in and confirms. xAI Grok, Anthropic, GitHub Copilot, Command Code, Cursor, Google Antigravity, and Kiro are explicitly marked Experimental compatibility. Installed-Host validation reached each Provider's authorization boundary and stopped before user consent; mock/fixture tests cover exchange or polling, refresh rotation, denial, timeout, cancellation, logout, route activation, and secret redaction.

Alpha v0.2.0-alpha.4 · exact compatibility target: official DSH 47f9438 · the self-contained bootstrap uses the official DSH plugin CLI and returns Web on its original port · release notes · MIT · community-maintained and not a DeepSeek or OpenAI product.

pnpm dlx github:Stormycry-cryp/dsh-AuthInOne#v0.2.0-alpha.4 install --profile web

The command is owned by this package. It validates the running standard DSH Host, calls the official dsh plugin add path, then replaces that Host on the same URL. It does not require a patched DSH core, a manual profile edit, a second Web instance, or a temporary port. See Install, upgrade, and remove for source-checkout and non-default-port forms.

If AuthInOne is useful to you, a Star on GitHub is a welcome way to support the project.

Open DSH, then go to Settings → Models or Settings → Usage. The browser receives aggregated usage, redacted status, an authorization URL, and where required a user code. OAuth verifier, authorization code, device code, access token, and refresh token stay on the Host; the plugin never imports ~/.codex/auth.json, OpenCodex state, cookies, browser storage, OTPs, or another product's credentials.

Showing the opening section of the README — the full document lives in the repository以上为 README 开头摘要，完整文档在仓库内 · View the full README on GitHub →在 GitHub 查看完整 README →

渲染基于仓库 Stormycry-cryp/dsh-AuthInOne 的 README.md。 在 GitHub 查看原文 →

Related相关推荐

← 上一个 Prev dsh-plugin-cc 下一个 Next tokenbank →