modlens
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 actua
Оригинален текст · няма потвърден превод на българскиПърво прочетете инструкцията.
Файлът се зарежда от посочения източник само по ваше действие. Можете да го прочетете тук, да го копирате или да го запазите като .md.
GitHub хранилище- Звезди на репото
- 4019
- Лиценз
- MIT
- Последна проверка на записа
- 23.09.2026 г.
Добавете в своя инструмент.
Командата отваря избора на skills от репозитория. Прочетете файла и условията на автора преди изпълнение.
npx skills add liustack/modlensСтраницата копира текст. Не инсталира и не изпълнява нищо на устройството ви.
Откъс от SKILL.md
Началото на файла на автора, без превод.
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.1):
- A
modlensonPATHwhose major version is 3 and is at least 3.27.1:modlens <args>. - Otherwise, if
npxexists:npx --yes --package @liustack/modlens@3.27.1 modlens <args>. - Otherwise, if
bunxexists:bunx --bun @liustack/modlens@3.27.1 <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:
| You need | Do |
|---|---|
| What can run here, and why | modlens doctor (providers, failover chains, guard verdict, reusable harness vision; no quota) |
| Current settings | modlens config show |
First use and config show is empty | Follow references/onboard.md: inventory the machine, ask the user what to enable, configure only that |
| Set keys, providers, guard lists, reuse grants | references/configure.md has every key and recipe |
| A pasted image with no visible path | references/find-image.md has the branch for each harness |
| An error | Read the message: every error names its cause and most name the fix |