Introduction

In the DeepSeek Harness (DSH) ecosystem, when developing or using agents, it is often necessary to call GitHub, npm, or various API endpoints. These operations typically require a Token for authentication. Writing the Token directly into conversation history or creating local plaintext files does not comply with security practices. The dsh-token-vault plugin provides a solution: store the Token in DSH’s own credential record space and inject it via environment variables at runtime, ensuring that the secret never leaves the host.

Core Features

The plugin provides seven Agent-oriented tools for managing the lifecycle and usage of credentials:

  • vault_list: Lists the names of stored Tokens, without displaying any values.
  • vault_has: Checks whether a given Token exists.
  • vault_set: Stores or updates a Token; the input value is not echoed during execution.
  • vault_remove: Deletes the specified Token.
  • vault_import: Imports a Token from gh auth token (source: gh) or ~/.npmrc (source: npm).
  • vault_run: Runs a gh, npm, npx, node, or git command and injects the Token into the corresponding environment variable (github/gh → GH_TOKEN, npm/node → NPM_TOKEN, overridable via env_name).
  • vault_show: Only this path may expose the Token; you must set confirm: true when using it.

Installation and Enabling

The installation command is as follows. The plugin declares dsh.bundle.patch, so it will be mounted automatically after installation, but DSH Desktop must be restarted for changes to take effect.

dsh plugin --profile desktop add @yyfather/dsh-token-vault

After installation, you can manage Tokens in the following ways:
* Settings → Marketplace → Installed: Enable, update, or uninstall the plugin here.
* Settings → Credential Vault: Enter a Token or import existing credentials directly on this page.

Security Mechanisms

The security design of this plugin is based on three layers:

  1. Storage Layer: Uses DSH’s credential record space (path: dsh-token-vault/<name>) and performs atomic writes (modifyRecord), without generating any plaintext files.
  2. Usage Layer: vault_run only places the Token in the environment variables of the child process; the token value is not included in standard output, standard error, or log files.
  3. Control Layer: The plugin automatically injects the token-vault-usage prompt rule, requiring agents not to print or persist Tokens in conversations.

Typical Usage

When using vault_run, the agent automatically injects the environment variable to execute the command. For example, when invoking the gh tool, vault_run sets the GH_TOKEN environment variable, completing GitHub operations without exposing the Token in logs at all.

Applicable Scenarios and Notes

This plugin is suitable for scenarios that require securely calling external command-line tools (such as gh or npm) within the DSH environment. Since the plugin runs with the permissions of the current DSH process, it is recommended to review the source code and license before installation.

Conclusion

dsh-token-vault provides DeepSeek Harness with an end-to-end credential security solution, from storage to usage. For more details, source code, and directory information, please refer to the following links.

  • GitHub Repository: https://github.com/YYfather/dsh-token-vault
  • DSH Plugin Directory: https://www.skillhub.cn/plugins/YYfather/dsh-token-vault