Modlens vs Vision Router
These two listings overlap in this directory — they share a category or a use case, so they are candidates for the same job. Below is every field this directory checked, side by side: verification level, security scan, compatibility target and install command. Under the table: editorial notes on when to pick each side, and when neither is the right install.
Modlens
liustack
A vision bridge for text-only harnesses — images go out to a vision engine you configure, structured evidence comes back.
Read the listingVision Router
ysr666
Eyes for text-only agents — an opt-in vision turn with pixel-level tools, and an anonymous keyless fallback that is not private.
Read the listing| Field | Modlens | Vision Router |
|---|---|---|
| Verification | L2 · Structured | L3 · Install spec |
| Security scan | Unverified | Unverified |
| Health | Active | Active |
| dshTarget | — | 0.1.0-rc.8 through 0.1.5-rc.2 |
| Last checked | 2026-09-18 | 2026-09-18 |
| Licence | MIT | MIT |
| Language | TypeScript | JavaScript |
| Stars (context only) | 3,985 | 1,106 |
| Categories | Tools & Capabilities, Models & Reasoning | Tools & Capabilities, Models & Reasoning |
| Use cases | Vision & OCR | Vision & OCR |
| Install command | dsh plugin --profile web add @liustack/modlens | dsh plugin --profile web add dsh-vision-router |
Every row is a public field of the two listings. This page does not score plugin quality.
Scenario notes
Both give a text-only harness eyes, but they buy different guarantees. Modlens is a single evidence bridge: images leave for a vision engine you configure, structured JSON comes back, and the published install pins a version so downstream parsers do not break under you. VisionRouter is a turn-level toolkit — opt-in vision turns, pixel-diff tools, and a keyless anonymous fallback that is convenient and not private. Pick for the path your images take, not for star counts.
When to pick Modlens
Choose Modlens when every screenshot must travel through a provider you control, when parsers depend on a stable evidence schema, and when you would rather accept fewer tools than an anonymous endpoint. It is the better contract for production pipelines that already have vision API keys and a fixed prompt format.
When to pick Vision Router
Choose VisionRouter when the job is interactive screenshot work — pixel regression, ad-hoc inspection turns — and you want tools in the same install. Keep the keyless path off anything sensitive; if you need keyed access, configure it before the first load-bearing session, not after a leak.
When neither fits
Neither is a substitute for a native multimodal model. If your model already sees images well, you probably want review and citation tooling instead of another vision bridge. If you need long-page OCR as the primary task, look at Vision-Toolkit rather than forcing either of these into that role.
Which to pick
- Vision Router carries the higher verification level (L3 vs L2), meaning its install path was exercised further.
- They declare different harness targets (undefined vs 0.1.0-rc.8 through 0.1.5-rc.2); the older target may simply not have caught up with the current preview line.
- Modlens has the larger community (3,985 stars), though star counts measure attention rather than safety or quality.
Questions
- Are Modlens and Vision Router interchangeable?
- They overlap in what they do (they share at least one category or use case), but they differ in install path and how far they were checked: Modlens is L2, Vision Router is L3. Confirm the install command in the table above, then try it in an isolated profile.
- Which one is more current?
- Modlens was checked more recently (2026-09-18 against 2026-09-18). That date is when this directory last verified the listing, not when the plugin last shipped a release.
- Can I install both?
- Sometimes — if they do not fight for the same tool name or UI slot. Modlens is unverified and declares no harness target; Vision Router is unverified and declares 0.1.0-rc.8 through 0.1.5-rc.2. A later install that re-registers the same capability can silently override the first. Safer path: try each in an isolated profile, compare the registered tools, then combine only what does not collide.