DeepSeek Harness Plugin

XRC111/dsh-apikeys

Category Tools & Capabilities Added 2026-11-12

One credential store for many API platforms: keeps keys for GitHub, Cloudflare, Vercel, npm, Docker Hub, Hugging Face and custom platforms in the DSH credential store rather than in configuration or the session log, and gives the model three tools. apikey_call takes a path rather than a URL, so a key only reaches the host its platform fixes; apikey_platforms lists platforms and accounts without values; apikey_key gets, sets or clears one. Supports five auth shapes (bearer, custom header, x-api-key, basic, query string), verifies a key against the identity the platform returns, and reports transport failures as readable results instead of ending the turn. By default (exposeKeys on) the apikey_key tool can return a stored key's value to the model, which puts it in the session log; turn exposeKeys off to keep keys inside the Host.

Install

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

dsh plugin --profile web add github:XRC111/dsh-apikeys

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).

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.