vision-err

vision-err is a command for coding agents from spock-wen/vision-mcp-server. It costs 17 tokens per session (95 once invoked), scanned A, original, MIT.

A command for diagnosing error screenshots with a vision MCP server. It examines stack traces, console output, or error dialogs in an image and suggests fixes.

In plain words
What is it for?
Passing an image path and optional context to locate the likely cause of an error and get repair suggestions.
Why use it?
It helps when the problem is visible in a screenshot and copying the error text is inconvenient or incomplete.

Command

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add commands/spock-wen/vision-mcp-server/vision-err
Clone the repo
git clone --depth 1 https://github.com/spock-wen/vision-mcp-server

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for vision-err

README.md
[![agentmods](https://agentmods.dev/badge/commands/spock-wen/vision-mcp-server/vision-err.svg)](https://agentmods.dev/commands/spock-wen/vision-mcp-server/vision-err)
Your own site
<a href="https://agentmods.dev/commands/spock-wen/vision-mcp-server/vision-err"><img src="https://agentmods.dev/badge/commands/spock-wen/vision-mcp-server/vision-err.svg" alt="Measured on agentmods" height="20"></a>
Per session 17 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 95 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00017 $0.00095
Opus 5 $0.00009 $0.00048
Sonnet 5 $0.00003 $0.00019
Haiku 4.5 $0.00002 $0.00010

Measured 4d ago against content hash 44ed01a43ac6, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

vision-err scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

commands/vision-err.md · 8 lines

What it actually says

调用 MCP 工具 diagnose_error_screenshot,分析下面这张错误截图(堆栈/控制台/报错弹窗),定位原因并给出修复建议。请把用户输入里的图片路径识别为 image.path,额外的上下文描述可作为 context

$ARGUMENTS

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 4d ago First seen · 8 lines · 17 tokens per session scan A 44ed01a43ac6

Subscribe to this mod's changes

vision-err is a command published in the GitHub repository spock-wen/vision-mcp-server (0 stars, last pushed 1mo ago), licensed MIT. It adds 17 tokens to every session and 95 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.