What is spec-screenshot?

A command that examines website screenshots and writes a detailed implementation specification to SPEC.md. It checks whether screenshots are available and can use a deeper analysis mode when requested.

Use it to document a screenshot's page structure, grid, navigation, sections, and visual design before implementing the website.

It turns a visual reference into written guidance about layout, spacing, components, and other details developers need to rebuild the page.

spec-screenshot — Command for Claude Code by sablier-labs

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.

Clone the repo

git clone --depth 1 https://github.com/sablier-labs/plugin-marketplace

Made for: Claude Code.

Or install frontend, the plugin that ships this one along with the rest of its 3 skills, 1 command.

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/sablier-labs/plugin-marketplace/spec-screenshot/github.svg)](https://agentmods.dev/commands/sablier-labs/plugin-marketplace/spec-screenshot)

Your own site

<a href="https://agentmods.dev/commands/sablier-labs/plugin-marketplace/spec-screenshot"><img src="https://agentmods.dev/badge/commands/sablier-labs/plugin-marketplace/spec-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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/sablier-labs/plugin-marketplace/spec-screenshot"><img src="https://agentmods.dev/badge/commands/sablier-labs/plugin-marketplace/spec-screenshot.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 8 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 4,051 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.

Model	Per session	Once invoked
Fable 5.1	$0.00008	$0.04051
Opus 5	$0.00004	$0.02025
Sonnet 5	$0.00002	$0.00810
Haiku 4.5	$0.00001	$0.00405

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

Security

Grade A, and why

spec-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 8d 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.

plugins/frontend/commands/spec-screenshot.md · 580 lines

How it starts

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

Context

Current directory: !pwd
Target output: !test -f SPEC.md && echo "SPEC.md exists (will be overwritten)" || echo "Will create new SPEC.md"
Arguments: $ARGUMENTS
Thinking mode: !echo "$ARGUMENTS" | grep -q -i "--deep|deep" && echo "DEEP (sequential thinking enabled)" || echo "STANDARD (regular analysis)"

Your Task

STEP 1: Validate prerequisites

CHECK for images in conversation history:

SCAN recent messages for screenshots or images
IF no images found: ERROR "No screenshots detected in conversation. Please paste website screenshots before running this command."
IF images found: LOG "Found screenshots ready for analysis"

STEP 2: Perform ultra-detailed analysis

DETERMINE thinking mode from arguments:

IF $ARGUMENTS contains "deep" or "--deep": USE sequential thinking tool (mcp__sequential-thinking__sequentialthinking)
ELSE (STANDARD mode): Perform regular analysis

Analysis framework - cover ALL of these aspects:

Layout Architecture
- Overall page structure (header, navigation, hero, main content, sidebars, footer)
- Grid system and column layouts
- Container widths and max-widths
- Section hierarchy and nesting
Typography System
- Font families (identify primary, secondary, monospace)
- Font sizes for each text level (h1-h6, body, small, etc.)
- Font weights used (light, regular, medium, semibold, bold)
- Line heights and letter spacing
- Text colors and contrast ratios
Color Palette
- Primary brand colors
- Secondary/accent colors
- Background colors (main, sections, cards)
- Text colors (headings, body, muted, links)
- Border colors
- State colors (success, error, warning, info)
- Color codes in hex/rgb (best approximation)
Spacing System
- Margins between major sections
- Padding within components
- Gap spacing in flex/grid layouts
- Consistent spacing scale (e.g., 4px, 8px, 16px, 24px, 32px)
- Vertical rhythm patterns

Read the full file on GitHub · 580 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.

8d ago First seen · 580 lines · 8 tokens per session scan A 0d2224bf742d

Subscribe to this mod's changes

spec-screenshot is a command published in the GitHub repository sablier-labs/plugin-marketplace (7 stars, last pushed 2mo ago), licensed MIT. It adds 8 tokens to every session and 4,051 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.

Design and UX Frontend

seed-create-component

A command for creating a new SEED Design component, including its source specification, recipes, React implementation, documentation, examples, and optional headless layer.

daangn/seed-design · 12 tokens

sddesign

Full spec-driven pipeline — walks brief → tokens → shape (spec) → craft (build) → converge → ship in one guided run. Writes .ui-craft/spec.md. Run when starting a net-new surface from scratch.

educlopez/ui-craft · 46 tokens

craft

One-shot build pipeline for a complete surface from an outcome recipe — inputs (or defaults) → composition → theme → build order → acceptance bar. Use when the user asks for a whole surface ("build me a dashboard", "I need a landing page") and expects a shippable result, not component-level help.

educlopez/ui-craft · 64 tokens

spec-screenshot