DeepSeek Harness Plugin

173787247/dsh-wsl-secret

Stars ★ 1 Category WSL & Windows Interop Added 2026-09-24

Read-only pass / age secrets with allowPrefixes; reveal defaults to false.

Install

# from GitHub (first run asks for allowBuilds approval — follow the hint, retry)

dsh plugin --profile web add github:173787247/dsh-wsl-secret

Any plugin you install runs third-party code with your own permissions — it can read your files, use your credentials, and reach the network, and tool approvals don’t sandbox it. GitHub-sourced plugins also run build scripts at install time — pnpm blocks those until you allow them, so an install can stop with ERR_PNPM_GIT_DEP_PREPARE_NOT_ALLOWED or ERR_PNPM_IGNORED_BUILDS; dsh prints the exact key to add under allowBuilds in your profile’s pnpm-workspace.yaml, and the install works on the next run. Allowing a build is a trust decision: only install sources you trust, and pin a commit (github:owner/repo#sha).

README

Languages: 中文(首页) · English (this file)

Read pass / age secrets into a DSH (Cordis) session — safely.

npm dsh-wsl-secret
Requires WSL/Linux with pass and/or age on PATH
Default reads blocked until you set allowPrefixes

Why this plugin exists

  • dsh-wsl-cred → Git push/pull credential hints only
  • dsh-wsl-secret → App secrets (OpenRouter, Discord bot token, …) from your password store

If secret_status shows ready=false, the plugin is installed but not configured. That is intentional.

5-minute setup

1. Install tools (once)

# Debian/Ubuntu example
sudo apt install pass age
# initialise pass if needed: pass init <gpg-id>

2. Put secrets under one prefix

pass insert dsh/openrouter    # paste API key, first line = secret
pass insert dsh/discord-bot

3. Allow that prefix in Cordis

Edit your profile cordis.patch.yml (example: ~/.dsh/profiles/web/cordis.patch.yml):

plugins:
  dsh-wsl-secret:
    enabled: true
    path: /mnt/c/Users/YOU/Desktop/AIFullStackDevelopment/dsh-wsl-secret
    config:
      # pass: folder names under ~/.password-store
      # age: absolute or ~/ filesystem roots
      allowPrefixes:
        - dsh
        # - ~/secrets
      reveal: false          # keep false; use secret_to_env instead
      timeoutMs: 15000

Restart DSH / reload the profile.

4. Agent flow (what to ask / what tools do)

Step Tool Result
Check secret_status ready=true, lists allowPrefixes
Find secret_pass_list names only, e.g. dsh/openrouter
Confirm secret_pass_exists { exists: true }
Use secret_to_env sets process.env.OPENROUTER_API_KEY, returns preview only
Optional secret_pass_get preview (or full value only if reveal: true — avoid)

Example tool call:

{ "name": "secret_to_env", "arguments": {
  "name": "dsh/openrouter",
  "envKey": "OPENROUTER_API_KEY"
}}

After that, other tools in the same dsh process can read process.env.OPENROUTER_API_KEY. The chat UI only sees a redacted preview.

Tools

Tool Purpose
secret_status pass/age on PATH + allowlist + ready
secret_pass_list list entry names under allowlist
secret_pass_exists boolean exists check
secret_to_env preferred — pass → process.env
secret_pass_get read with preview / optional reveal
secret_age_to_env age file → process.env
secret_age_decrypt decrypt age file (preview / reveal)

Security model

  1. Empty allowPrefixes → every read fails (safe default).
  2. Pass names must match an allowlist prefix (dshdsh/...).
  3. Age paths must sit under filesystem roots in the same list (~/secrets/...).
  4. reveal: false (default): tool results never include the full secret.
  5. Prefer secret_to_env / secret_age_to_env so the model never needs the raw string in context.
  6. Never paste secrets into the chat.

Develop

npm test

License

MIT — LICENSE

Content from the project README on GitHub ↗

Links

More in this category

View the whole category →

Community comments

Comments are public GitHub Discussions. Loading them connects to GitHub and Giscus; a GitHub account is required to post.