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 marc0der/reveng --skill image-to-htmlgit clone --depth 1 https://github.com/marc0der/revengWrote 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/marc0der/reveng/image-to-html)<a href="https://agentmods.dev/skills/marc0der/reveng/image-to-html"><img src="https://agentmods.dev/badge/skills/marc0der/reveng/image-to-html/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/marc0der/reveng/image-to-html"><img src="https://agentmods.dev/badge/skills/marc0der/reveng/image-to-html.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.00048 | $0.00681 |
| Opus 5.5 | $0.00019 | $0.00272 |
| Sonnet 5.5 | $0.00010 | $0.00136 |
| Haiku 4.5 | $0.00005 | $0.00068 |
Grade A, and why
image-to-html 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 — 39 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are converting a legacy application screenshot into semantic, unstyled mockup HTML.
Input
The image file path is: $ARGUMENTS
Steps
-
Read the image using the Read tool. The path is relative to the project root.
-
Analyse the UI shown in the screenshot. Identify all structural elements: headings, navigation, forms, tables, buttons, lists, sections, and any other meaningful components.
-
Produce semantic HTML following these rules strictly:
- Use appropriate semantic elements:
<header>,<nav>,<main>,<section>,<form>,<table>,<fieldset>,<legend>,<label>,<button>,<h1>–<h6>,<ul>/<ol>,<footer>,<aside>,<article>,<details>,<summary>, etc. - Do NOT include any
<style>tags, inline styles, or CSS classes used for visual purposes. - Use
aria-labelor similar attributes only where they convey meaningful information not already present in the text content. - Preserve all visible text content exactly as shown in the screenshot, except for personally identifiable information (PII) — replace any real names, email addresses, phone numbers, national identifiers, addresses, or other identifying details with realistic fake equivalents (e.g. "John Smith" → "Jane Cooper", "[email protected]" → "[email protected]"). Keep the fake data consistent within a single file (i.e. the same real name always maps to the same fake name).
- Represent form fields with appropriate input types (
text,email,date,checkbox,radio,select, etc.). - Use
<table>with<thead>,<tbody>,<th>, and<td>for tabular data. - Add HTML comments to describe non-text visual elements (icons, charts, images, logos) that carry meaning — e.g.
<!-- Bar chart showing monthly revenue -->. - Wrap the content in a minimal HTML5 document structure (
<!DOCTYPE html>,<html lang="en">,<head>,<body>). - Set the
<title>to something descriptive derived from the page content.
- Use appropriate semantic elements:
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 · 39 lines · 48 tokens per session scan A 78df9e22ad05
image-to-html is a skill published in the GitHub repository marc0der/reveng (5 stars, last pushed 5mo ago), licensed MIT. It adds 48 tokens to every session and 681 once invoked, about $0.0002 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
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…