Plugin directory / Developer / opencode-usage
opencode-usage
Verified · install-tested on dsh AmaTsumeAkira
What it does
OpenCode Go quota badge plugin (dsh bundle) | OpenCode Go quota badge plugin for dsh
Works — verified, early-stage project
OpenCode Go quota badge plugin (dsh bundle) | OpenCode Go quota badge plugin for dsh It installs cleanly and boots without issues in our testing. It's early-stage but functional.
“Verified” means our automated CI actually ran dsh plugin add in a clean profile and it booted — nothing more. Feature descriptions and version compatibility are the author’s claims. This is not a security audit and not an endorsement of third-party code.
README
opencode-usage
English | 中文
OpenCode Go quota badge plugin (bundle) — shows rolling / weekly / monthly quota usage and reset times for OpenCode Go right in the dsh Web UI.
Screenshot


Features
- Renders the three quota windows (rolling / weekly / monthly) as colored percentages (green → amber → red by usage) with reset countdowns in the composer dock
- Shows the last fetch time ("updated M/D HH:mm"), switching to "updating…" while a refresh is in flight
- Click the "OpenCode Go" label to refresh the quota manually
- Auto-refreshes every 5 minutes
- The API key lives only inside the harness process: resolved per request through the credentials service, passed to curl via an environment variable, never serialized to the browser or logs
Install
This package follows the official dsh bundle format: it ships prebuilt artifacts (lib/ is committed to the repo) and has no install scripts, so a git install needs no pnpm allowBuilds grant.
dsh plugin --profile web add github:AmaTsumeAkira/opencode-usage
Or install from a local directory:
dsh plugin --profile web add ./opencode-usage
Uninstall:
dsh plugin --profile web remove opencode-usage
Credentials
The plugin reads OPENCODE_GO_API_KEY through the official credentials service (either the environment or ~/.dsh/.credentials.yaml):
# ~/.dsh/.credentials.yaml
OPENCODE_GO_API_KEY: your-opencode-go-api-key
Without a configured key the badge shows "获取失败" (fetch failed).
Layout
opencode-usage/
├── package.json # dsh.bundle + dsh.client(web) manifest
├── cordis.patch.yml # plugin row insertion layer
├── lib/index.js # host half: /opencode-usage route (ESM, zero deps)
└── lib/client.js # browser half: composer-dock badge (__ModuleLoader__ format)
License
MIT
Install
Install the catalog once, then DeepSeek Harness can find and install any plugin from this site automatically:
dsh plugin add dshbase-catalog Then say "install opencode-usage for me" — your agent finds it in the directory and installs it. Docs: dshbase-catalog · verified packs.
Web profile:
dsh plugin --profile web add opencode-usage Headless (CLI) profile:
dsh plugin --profile headless add opencode-usage Package
npm: opencode-usage · version — · tested on dsh 0.1.0-rc.6
Test report
Verified end-to-end: L1 install + L2 load + L3 runtime Q&A on dsh 0.1.0-rc.6.
When to use it
Extend the agent's coding surface — give it a new tool, workflow, or integration so it handles a dev task it couldn't before.
Who it's for
Developers who want dsh to behave like a teammate on real codebases — editing, running, and verifying changes rather than just answering.
For developers — extending it
The tool/command surface is the seam: expose more of the SDK, add smarter context wiring, or tighten the loop between code changes and verification.