Vision for Text Models
Lets text-only models read images from paths or URLs through a vision tool.
Install
npx skills add liustack/modlens --skill modlens -g -a claude-code -y- Repository
- liustack/modlens4.7k
- Category
- AI and agents
- Updated
- 12d ago
- License
- MIT
- Context cost
- Lightabout 1,046 tokens
- Runs scripts
- Yes, review before use
What it does
Plug-in vision for text-only models. Hard rule: when a file path or URL with an image extension (.png, .jpg, .jpeg, .webp, .gif, .heic, .heif) appears anywhere in the conversation (typed by the user, injected as a `[Image: source: <path>]` line, or inside a tag) and you cannot see that image's content, run this skill on it before any other approach: no self-built OCR, no PIL, no tesseract. Also triggers on pasted-image placeholders such as `[Image #1]` and `[Unsupported Image]`. If you can actually see the image, do not use this skill. When unsure, run `modlens guard` before the first read of a session: a deny verdict means the active model has native vision and must read the image itself. Runs the modlens CLI to convert the image into structured JSON evidence: every word transcribed, layout regions, semantics, visual clues. Also use when the user asks how to install, configure, or switch modlens providers (Gemini API key, OpenAI-compatible endpoints, Claude API or Claude Code CLI).
ModLens, Vision Bridge Skill
Use this skill when an image is in play and you cannot see its content: a path or URL with an image extension (the path alone is the trigger, hand it to modlens, never Read the bytes or build your own OCR), a placeholder like [Image #1], [Unsupported Image], or a [Image: source: <path>] line, or the user asking to configure modlens. Do not use it for web search or fetch (that is modsearch), or for images you can already see natively.
Run it
Every modlens command goes through the launcher bundled with this skill. Replace <skill-dir> with the directory this SKILL.md lives in:
bash <skill-dir>/scripts/run.sh <args> # macOS / Linux
powershell -ExecutionPolicy Bypass -File <skill-dir>\scripts\run.ps1 <args> # Windows
It resolves a working runtime (PATH modlens, then npx, then bunx) and forwards your arguments unchanged. Exit 78 means no runtime: relay the nextSteps from its stderr JSON instead of retrying.
If your harness forbids running scripts, reason through the same order by hand and run the first line that works (the pinned version is 3.27.2):
- A
modlensonPATHwhose major version is 3 and is at least 3.27.2:modlens <args>. - Otherwise, if
npxexists:npx --yes --package @liustack/modlens@3.27.2 modlens <args>. - Otherwise, if
bunxexists:bunx --bun @liustack/modlens@3.27.2 <args>. - Otherwise tell the user no JavaScript runtime was found and that installing Node 22.19+ (https://nodejs.org) or Bun (https://bun.sh) is the next step. Do not claim modlens itself failed.
references/runtime.md documents the pin and the diagnostic fields.
Ask the CLI, not this file
State lives on the machine and the CLI reports it; read what you need when you need it:
