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 furqanistic/aura-skills --skill screenshot-to-codegit clone --depth 1 https://github.com/furqanistic/aura-skillsWrote 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/furqanistic/aura-skills/screenshot-to-code)<a href="https://agentmods.dev/skills/furqanistic/aura-skills/screenshot-to-code"><img src="https://agentmods.dev/badge/skills/furqanistic/aura-skills/screenshot-to-code/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/furqanistic/aura-skills/screenshot-to-code"><img src="https://agentmods.dev/badge/skills/furqanistic/aura-skills/screenshot-to-code.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.00123 | $0.02333 |
| Opus 5 | $0.00062 | $0.01167 |
| Sonnet 5 | $0.00025 | $0.00467 |
| Haiku 4.5 | $0.00012 | $0.00233 |
Grade A, and why
screenshot-to-code 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 11d 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 — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Screenshot to Code
Treat the screenshot as visual evidence, not merely inspiration. Reproduce its design language and visible behavior while keeping the implementation responsive, accessible, and maintainable.
Operating standard
Work in five gated phases. Do not skip directly from seeing the screenshot to polishing CSS:
- Discover — understand the screenshots, repository, target route, available assets, and runtime.
- Specify — turn visual evidence into layout, token, component, content, state, and responsive decisions.
- Construct — build semantic structure and correct macro geometry before fine styling.
- Compare — render at controlled viewports and measure differences against the references.
- Refine — fix the highest-impact mismatch, recapture, and repeat until the completion gate passes.
Favor visual fidelity over personal design preference, and engineering quality over screenshot-only hacks. A strong result must satisfy both.
Start with context
- Open and inspect every attached screenshot at full resolution. Record its pixel dimensions, orientation, visible browser/device chrome, crop, content density, and likely CSS viewport.
- Inspect the repository before coding. Identify framework, routing, styling approach, component library, design tokens, fonts, assets, breakpoints, testing tools, and the correct page or component entry point.
- If a matching implementation exists, render it and improve it incrementally. Preserve established architecture and working behavior.
- If starting from scratch, use the user's requested stack. Otherwise prefer the repository's existing stack; do not replace it just for convenience.
- Ask only for information that cannot be safely inferred and would materially change the result, such as an unreadable key asset or unknown target route.
For multiple screenshots, map each image to a route, viewport, UI state, and shared shell. Determine whether they show separate pages, responsive variants, modal/menu states, or steps in one flow. Do not implement each screenshot as an unrelated page when evidence shows a common system.
What ships with it
9 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.
- agents/openai.yaml 232 B
- references/assets-and-content.md 1.8 KB
- references/fidelity-rubric.md 2.0 KB
- references/frontend-quality.md 2.7 KB
- references/interaction-and-states.md 2.1 KB
- references/project-and-architecture.md 2.8 KB
- references/responsive-and-accessibility.md 3.8 KB
- references/verification-loop.md 1.6 KB
- references/visual-analysis.md 1.9 KB
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.
- 11d ago First seen · 156 lines · 123 tokens per session scan A b58ed85cde14
screenshot-to-code is a skill published in the GitHub repository furqanistic/aura-skills (5 stars, last pushed 22d ago), licensed MIT. It adds 123 tokens to every session and 2,333 once invoked, about $0.0006 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 skills, from other repositories
chakra-ui-builder
Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…
visual-ralph
Visual Ralph orchestration for frontend UI from generated references, static references, or live URL targets, using $ralph with built-in visual verdict and pixel-diff evidence until the implementation matches and leaves a reproducible design system.
frontend-visual-qa
Audits already-rendered web, landing-page, HTML deck/slide, browser tool/game, dashboard/admin, design-system, and desktop UIs using real-browser or native-app journeys, inspected screenshots, DOM geometry, responsive or projection viewports, and a bundled Playwright sweep. Use after UI implementation to find…
prototype-web
A clickable, high-fidelity web product prototype with navigation, a hero section, feature cards, steps, social proof, and optional pricing. It is designed to resemble a finished landing page while remaining a prototype.
animation-principles
Apply animation principles — easing, staging, follow-through — to one specific UI motion. Use when tuning how an animation feels. For product-wide duration and easing tokens use motion-system (design-systems); for a full interaction spec use micro-interaction-spec.
refactoring-ui
Audit and fix visual hierarchy, spacing, color, and depth in web UIs. Use when the user mentions "my UI looks off" (or amateur/unprofessional), "fix the design", "Tailwind styling", "color palette", "visual hierarchy", "design system", "spacing scale", or "component styling". Also trigger when building consistent…