Plugin directory / Developer / dsh-mimo-vision-hint
dsh-mimo-vision-hint
Verified · install-tested on dsh Isekai-Mfu
What it does
DSH plugin: dispatch image-recognition tasks to an opencode-go mimo-v2.5 subagent via system-prompt injection
Works — verified, early-stage project
DSH plugin: dispatch image-recognition tasks to an opencode-go mimo-v2.5 subagent via system-prompt injection 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
dsh-mimo-vision-hint
A zero-dependency hint plugin for DeepSeek Harness (DSH). It registers a section in the model's system prompt instructing the agent to dispatch image-recognition tasks to an opencode-go mimo-v2.5 subagent (a single-agent workflow with provider/model overrides) instead of reading images itself via read_image; if the workflow call fails, the agent falls back to read_image.
This plugin only injects prompt text: it registers no model tools and provides no cordis services, so mounting it in an agent composition needs no isolate realm.
Prerequisites
- Your DSH deployment has a provider named
opencode-goconfigured, serving amimo-v2.5model — the subagent dispatch targets that provider/model pair. - The active agent preset includes the workflow tool (needed to spawn the subagent).
Without these, the plugin does no harm: the injected prompt tells the agent to fall back to read_image directly.
Installation
This package is a DSH profile bundle (its manifest declares dsh.bundle and it ships its own mount layer), so the official plugin command installs and mounts it in one step — no hand-edited YAML required:
dsh plugin --profile web add github:Isekai-Mfu/dsh-mimo-vision-hint
dsh plugin installs the package into the profile's node_modules, records the dependency, and — because this package declares a bundle — automatically appends its layer (cordis.patch.yml, a single insert entry) to the profile's dsh.profile.bundles composition stack. The plugin then mounts at the host layer and takes effect for every new session of every agent preset in the deployment.
pnpm must be on your PATH (dsh plugin forwards to it). Uninstalling is equally one command — once the dependency is gone, the bundle layer leaves the composition stack automatically:
dsh plugin --profile web remove dsh-mimo-vision-hint
Manual installation (without pnpm)
- Place this package somewhere the profile can resolve (e.g.
$DSH_HOME/profiles/web/node_modules/dsh-mimo-vision-hint). - Add an insert entry to the profile's user patch layer (
$DSH_HOME/profiles/web/cordis.patch.yml):
- insert:
- id: mimo-vision
name: dsh-mimo-vision-hint
- Saving takes effect immediately (hot reload); remove the entry to disable.
Notes
No other dependencies, no configuration options. The prompt text is injected into every new session; the vision subagent's provider (opencode-go) and model (mimo-v2.5) are currently hard-coded — edit SECTION in lib/index.js to change them. Presets without the workflow tool (e.g. minimal mode) cannot dispatch the subagent; the prompt tells the model to fall back to read_image in that case.
License
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 dsh-mimo-vision-hint for me" — your agent finds it in the directory and installs it. Docs: dshbase-catalog · verified packs.
This plugin is GitHub source (not published to npm) — install it straight from the repo:
Web profile:
dsh plugin --profile web add github:Isekai-Mfu/dsh-mimo-vision-hint Headless (CLI) profile:
dsh plugin --profile headless add github:Isekai-Mfu/dsh-mimo-vision-hint Test report
Verified: L1 install + L2 load + L3 runtime from GitHub source 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.