screenshot-docs

screenshot-docs is a skill for Claude Code, Codex from vosslab/vosslab-skills. It costs 54 tokens per session (3,087 once invoked), scanned A, original, MIT.

A documentation tool that captures screenshots or short GIF demonstrations of a graphical interface, command-line tool, or web app and embeds them in project docs.

In plain words
What is it for?
Use it to add or refresh images under docs/screenshots/, managed screenshot sections in README.md and docs/, and the scripts or tests needed to reproduce the captures.
Why use it?
It gives first-time visitors visual proof of how an application looks or behaves, especially when written instructions are not enough.

Skill for Claude CodeCodex

Written for Claude Code and Codex: shipped in a Claude Code plugin, but also agents/openai.yaml present. Also seen: mentions subagents.

Part of the vosslab-skills plugin — 42 skills, 14 agents shipped together

Good fit Use it to add or refresh images under docs/screenshots/, managed screenshot sections in README.md and docs/, and the scripts or tests needed to reproduce the captures.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/vosslab/vosslab-skills/screenshot-docs
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.

Any agent
npx skills add vosslab/vosslab-skills --skill screenshot-docs
Clone the repo
git clone --depth 1 https://github.com/vosslab/vosslab-skills

Made for: Claude Code, Codex.

Or install vosslab-skills, the plugin that ships this one along with the rest of its 42 skills, 14 agents.

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 screenshot-docs

README.md
[![agentmods](https://agentmods.dev/badge/skills/vosslab/vosslab-skills/screenshot-docs/github.svg)](https://agentmods.dev/skills/vosslab/vosslab-skills/screenshot-docs)
Your own site
<a href="https://agentmods.dev/skills/vosslab/vosslab-skills/screenshot-docs"><img src="https://agentmods.dev/badge/skills/vosslab/vosslab-skills/screenshot-docs/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.

agentmods 80×15 button for screenshot-docs

Your own site · 80×15
<a href="https://agentmods.dev/skills/vosslab/vosslab-skills/screenshot-docs"><img src="https://agentmods.dev/badge/skills/vosslab/vosslab-skills/screenshot-docs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 54 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,087 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00054 $0.03087
Opus 5 $0.00027 $0.01543
Sonnet 5 $0.00011 $0.00617
Haiku 4.5 $0.00005 $0.00309

Measured 8d ago against content hash f1e4580b1ce8, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

screenshot-docs 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 8d ago.

The scan reads SKILL.md. This mod also ships 9 executable files (scripts/capture_cli.sh, scripts/capture_local.sh, scripts/capture_region.sh, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

skills/documentation/screenshot-docs/SKILL.md · 281 lines

How it starts

The opening of the file, as written. The whole thing — 281 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Screenshot docs

Overview

Capture static screenshots or short animated demonstrations of an app and embed them into README.md and docs/ files to make GitHub landing pages informative for first-time visitors.

This skill runs in Wave 2 of the docset-updater refresh, after readme-docs writes an empty managed screenshot block. It detects the app kind, chooses whether a static state or short interaction best proves the project's value, captures with the matching backend, stores the result under docs/screenshots/, and rewrites the inside of that block with real embed lines.

Behavioral contract

This skill writes to:

  • PNG and GIF files under docs/screenshots/.
  • The managed screenshot block in README.md and docs/ files (the lines between the begin and end sentinels).
  • Reproducible capture infrastructure in the target repository's established support location, such as scripts/ or tests/visual/.

Scope changes to documentation visuals, managed embed blocks, and their capture infrastructure. Treat app implementation code as read-only throughout. Prepare a changelog-ready summary for the caller or human maintainer to apply after capture.

Run the embed step idempotently: rewriting the block with the same captures yields identical output, so a repeat run against matching UI leaves files untouched. See the "Managed screenshot block" section in references/embedding.md for the exact format and replace algorithm.

In a headless or unavailable capture environment:

  • Add a "Known gaps" line to the verification report noting that capture was skipped.
  • Preserve existing screenshots and the existing managed block in place.
  • Preserve both block sentinels for the next run.
  • Continue with metadata, freshness, and verification steps supported by the current environment.

Wave role

In the docset-updater refresh, readme-docs runs in Wave 1 and screenshot-docs runs in Wave 2:

  1. readme-docs runs first and writes the empty managed block:
    • <!-- screenshots:begin (managed by screenshot-docs) -->
    • <!-- screenshots:end -->
  2. screenshot-docs runs as a second pass: captures visuals, writes PNGs or GIFs to docs/screenshots/, and rewrites the lines between the two sentinels with real embed lines, keeping the sentinels intact.

Read the full file on GitHub · 281 lines

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. 8d ago First seen · 281 lines · 54 tokens per session scan A f1e4580b1ce8

Subscribe to this mod's changes

screenshot-docs is a skill published in the GitHub repository vosslab/vosslab-skills (2 stars, last pushed 12d ago), licensed MIT. It adds 54 tokens to every session and 3,087 once invoked, about $0.0003 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens