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 skills add shabaraba/vibing.nvim --skill remote-screenshotgit clone --depth 1 https://github.com/shabaraba/vibing.nvimWrote 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/skills/shabaraba/vibing.nvim/remote-screenshot)<a href="https://agentmods.dev/skills/shabaraba/vibing.nvim/remote-screenshot"><img src="https://agentmods.dev/badge/skills/shabaraba/vibing.nvim/remote-screenshot/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/shabaraba/vibing.nvim/remote-screenshot"><img src="https://agentmods.dev/badge/skills/shabaraba/vibing.nvim/remote-screenshot.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.1 | $0.00092 | $0.00709 |
| Opus 5.5 | $0.00037 | $0.00284 |
| Sonnet 5.5 | $0.00018 | $0.00142 |
| Haiku 4.5 | $0.00009 | $0.00071 |
Grade A, and why
remote-screenshot 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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Screenshotting Neovim in the web container
Applies only to Claude Code on the web. CLAUDE_CODE_REMOTE must be true; the script
refuses to run otherwise and that refusal is correct, not an obstacle to work around. If you are
on a local machine, stop and say so — the user can see their own editor, and starting a hidden
second Neovim to photograph it helps nobody.
The sequence
S=scripts/screenshot
$S/capture.sh start --cols 150 --rows 40 lua/vibing/core/utils/git_snapshot.lua
$S/capture.sh keys ':VibingChat right' Enter
$S/capture.sh shoot /tmp/shot.png
python3 $S/pxbox.py /tmp/shot.png --expect-height 798 # (rows - 2) * 21
$S/capture.sh stop
Then hand the PNG to the user with SendUserFile.
capture.sh shoot prints the exact pxbox.py command to run. Run it. A capture whose
bottom rows were clipped is a plausible-looking screenshot of a slightly different screen, and
the difference between 21px and 1px of painted height does not survive downscaling — you will
not catch it by looking, and you will describe a statusline that is not in the image. pxbox.py
exits non-zero when the painted region is short.
scripts/screenshot/README.md has the mechanism, the headless_shell trap, and why each
terminal cell is its own element. Read it if something renders wrong.
Do not fabricate the contents
capture-pane returns the actual screen buffer, which is the whole point: the frontmatter,
statusline path and highlighting in the image are Neovim's own output. Two ways to throw that
away, both of which produce an image that lies:
- Writing a transcript into the chat buffer to make it look busy. Text you typed is not the
renderer's output. If a screenshot needs a real assistant turn — tool headers,
### Modified Files, streaming — that costs real tokens, so ask first and say that is what the image shows. - Describing what the screenshot shows without reading it back. Open the PNG and look before you narrate it.
Typing an unsent ## User message is fine and authentic — that is a real editor state a
user reaches by typing.
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.
- 1mo ago First seen · 61 lines · 92 tokens per session scan A 0f94359d2bc2
remote-screenshot is a skill published in the GitHub repository shabaraba/vibing.nvim (13 stars, last pushed today), licensed MIT. It adds 92 tokens to every session and 709 once invoked, about $0.0004 per session on Opus 5.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-09-04.
Other skills, from other repositories
mermaid-diagram
Use when the user asks for a flowchart, architecture diagram, sequence diagram, ER diagram, state machine, gantt chart, or any visual that fits Mermaid syntax. Hope Agent's chat renders Mermaid blocks natively, so the diagram appears inline.
visualize
Render a polished visual inline in the chat as part of your answer — a diagram, a chart, an interactive explainer, or a UI mockup. Load it proactively whenever an explanation would land better as a picture than as prose. Do not wait to be asked.
vellum-workspace-theme
Customize the app's visual theme — author design-token overrides (accent, background, surfaces, text, message-bubble colors) in the workspace ui/theme.json, validated by the assistant runtime and applied live to connected clients. Covers the token slots, the all-or-none override groups, the contrast floor, and reading…
vellum-avatar
Customize the assistant's avatar - build a native character, upload an image, or generate one with AI.
screen-annotation
Point at things on the screen the user is showing you.
design-review
Use when a design artifact or revision needs a prepared review packet or an evidence-backed record of a review outcome, requirements, and decisions.