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.
npx agentmods add commands/dashpot4/grok-plugin-for-claude/visiongit clone --depth 1 https://github.com/dashpot4/grok-plugin-for-claudeWrote 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.
[](https://agentmods.dev/commands/dashpot4/grok-plugin-for-claude/vision)<a href="https://agentmods.dev/commands/dashpot4/grok-plugin-for-claude/vision"><img src="https://agentmods.dev/badge/commands/dashpot4/grok-plugin-for-claude/vision.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00009 | $0.00137 |
| Opus 5 | $0.00005 | $0.00068 |
| Sonnet 5 | $0.00002 | $0.00027 |
| Haiku 4.5 | $0.00001 | $0.00014 |
Grade A, and why
vision 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.
What it actually says
Use Grok to analyze or describe an image (vision).
Examples:
/grok:vision ./screenshot.png/grok:vision ./design.png what are the main UI issues?/grok:vision ./chart.jpg extract the data as text
Foreground:
!node "${CLAUDE_PLUGIN_ROOT}/scripts/grok-companion.mjs" task "grok analyze image $ARGUMENTS"
This passes the image path to Grok for vision processing.
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.
- 4d ago First seen · 17 lines · 9 tokens per session scan A b723cf3f0f44
vision is a command published in the GitHub repository dashpot4/grok-plugin-for-claude (4 stars, last pushed 4d ago), licensed Apache-2.0. It adds 9 tokens to every session and 137 once invoked, about $0.0000 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.
Other commands, from other repositories
me-build-slides
Build a graphics-first thermal-fluid research presentation with slide-to-slide logic, visual plans, speaker notes, and backup-slide structure.
critique
Run a Grok Build critique that challenges the implementation approach and design choices.
video-maker
코드로 영상을 만들어요. React 기반 Remotion으로 프로그래밍 영상 제작.
check
Check whether the local Grok Build CLI is ready for the Claude Code bridge.
review
Run a read-only Grok code review against local git state.
adversarial-review
Run a skeptical, adversarial Grok code review against local git state.