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 ytvee-dev/webdev-agent-kit --skill design-screenshot-specgit clone --depth 1 https://github.com/ytvee-dev/webdev-agent-kitWrote 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/ytvee-dev/webdev-agent-kit/design-screenshot-spec)<a href="https://agentmods.dev/skills/ytvee-dev/webdev-agent-kit/design-screenshot-spec"><img src="https://agentmods.dev/badge/skills/ytvee-dev/webdev-agent-kit/design-screenshot-spec/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/ytvee-dev/webdev-agent-kit/design-screenshot-spec"><img src="https://agentmods.dev/badge/skills/ytvee-dev/webdev-agent-kit/design-screenshot-spec.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00035 | $0.02171 |
| Opus 5.5 | $0.00014 | $0.00868 |
| Sonnet 5.5 | $0.00007 | $0.00434 |
| Haiku 4.5 | $0.00003 | $0.00217 |
Grade A, and why
design-screenshot-spec 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 15d 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 — 211 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design Screenshot Spec
Purpose
Inspect live Figma designs or supplied screenshots, property panels, assets,
and notes to produce a traceable Design Implementation Spec. Review the
observed design as a product flow and resolve unspecified design and behavior
decisions with the user before handing affected work to an implementer.
The existing skill name remains stable for bundle compatibility.
When To Use
- The user sends screenshots of Figma frames, components, screens, or inspect panels.
- The user asks to analyze a visual design before implementation.
- The user provides a Figma file, frame, component, or prototype link and asks to inspect it or implement its design.
- The next step is frontend layout work and the implementer needs a structured spec.
When Not To Use
- The user asks to edit the design canvas, create files or whiteboards, generate a design system, or write Code Connect mappings.
- The user already provides a complete
Design Implementation Specand asks to implement it. Usefrontend-layout-implementer.
Required Context
- Read
AGENTS.md. - Confirm the classified task is
design-specor design intake for later frontend implementation. - Read
common/approved-patterns.md. - Read
common/anti-patterns.md. - Read
project/design-reference-profile.mdwhen present. - Read
references/spec-extraction-checklist.md. - For live links, read
references/design-source-inspection.md. - For effects or a visual-effect mismatch, read
references/effect-evidence.md. - After extraction, read
references/product-behavior-review.mdbefore formulating product questions or an implementation handoff.
Tool Contract
- Resolve
live_design_sourceanddesign_reference_filesthrough the current tool registry andtool-capabilities-manifest.jsonfor the active source. - A supplied link triggers scoped read-only inspection automatically: use a
permitted provider selected by the current explicit role/tool instruction;
otherwise use callable Figma MCP first with browser/computer-use fallback.
Apply
common/webdev-role-selection.mdfor an explicitly selected role. - Browser fallback must support screenshots and pointer interaction with the canvas and property panel. Search results or an HTTP fetch are not inspection.
- With screenshots and no link, inspect those images directly; do not require a Figma connection. Never invent a tool, session, node, or successful read.
- Follow host tool instructions and permissions. Do not install tools, change access settings, edit the source canvas, or write mappings during intake.
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 15d ago Changed · +10 lines 23faca51394f
- 1mo ago Changed · +32 lines · -3 tokens per session 93db8253cdeb
- 1mo ago First seen · 169 lines · 38 tokens per session scan A 5be2d0a5e09a
design-screenshot-spec is a skill published in the GitHub repository ytvee-dev/webdev-agent-kit (7 stars, last pushed 6d ago), licensed Apache-2.0. It adds 35 tokens to every session and 2,171 once invoked, about $0.0001 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-08-31.
Other skills, from other repositories
design-dna
Extract, define, and apply design DNA across three dimensions: design system (tokens), design style (qualitative feel), and visual effects (Canvas, WebGL, 3D, particles, shaders, scroll effects, etc.). Use this skill when: (1) a user wants to see the full 3-dimension design structure/schema, (2) a user provides…
hmi-design-full
Comprehensive ISA-101 design rules for Human Machine Interfaces in process automation, with detailed reference files covering color design, display hierarchy, navigation, alarms, human factors, performance, and lifecycle management. Use when designing, building, reviewing, or generating code for HMIs, control system…
harness-design
Quality harness for design-dna Phase 3 output with browser-based visual verification. After an agent generates a design from a Design DNA JSON + user content, this skill acts as a verification and scoring layer — collecting all page resources via console/network inspection, performing section-by-section screenshot…
hmi-design-light
ISA-101 design rules for Human Machine Interfaces in process automation, covering display hierarchy, color standards, alarm integration, navigation, and situation awareness. Use when designing, building, reviewing, or generating code for HMIs, control system displays, SCADA screens, operator dashboards, or industrial…
baoyu-diagram
Create professional, dark-themed SVG diagrams of any type — architecture diagrams, flowcharts, sequence diagrams, structural diagrams, mind maps, timelines, illustrative/conceptual diagrams, and more. Use this skill whenever the user asks for any kind of technical or conceptual diagram, visualization of a system…
understand-figma
Analyze a Figma file via the Figma REST API and generate an interactive design knowledge graph (pages, screens, components, component sets, instances, design tokens) with a kind:"design" dashboard.