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 agentmods add skills/chocpink123/prototype-previewer-skill/prototype-previewernpx skills add chocpink123/prototype-previewer-skill --skill prototype-previewergit clone --depth 1 https://github.com/chocpink123/prototype-previewer-skillWrote 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/chocpink123/prototype-previewer-skill/prototype-previewer)<a href="https://agentmods.dev/skills/chocpink123/prototype-previewer-skill/prototype-previewer"><img src="https://agentmods.dev/badge/skills/chocpink123/prototype-previewer-skill/prototype-previewer.svg" alt="Measured on agentmods" 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 | $0.00088 | $0.01024 |
| Opus 5 | $0.00044 | $0.00512 |
| Sonnet 5 | $0.00018 | $0.00205 |
| Haiku 4.5 | $0.00009 | $0.00102 |
Grade A, and why
prototype-previewer 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 4d 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prototype Previewer
Overview
This skill creates a reusable prototype review surface instead of a throwaway mock. The default output is a desktop review page with a left-side flow navigator, a center device or viewport preview, and a right-side review notes panel that stays synchronized with the active screen.
The same source material in this repo can also be reused in Cursor and Claude Code through the adapter files under adapters/.
Use this skill when the goal is fast product review, flow validation, or Figma handoff from a local web prototype.
Workflow
-
Inspect the repo or brief before writing anything. Infer the product type, primary entry screen, major branches, detail pages, empty states, loading states, and any bottom-nav or tab structure. Every independent page or state counts as its own
data-screen. -
Build or update
index.htmlas the interactive reviewer. The default structure should be:- left: clickable flow list with short summaries
- center: mobile device shell or browser viewport with stateful screens
- right: editable review notes for the active screen
-
Preserve the stable behavior recovered from prior sessions.
- Use English for visible UI labels and review notes by default.
- If another language is needed, require it explicitly in the prompt.
- Interactions are local-only JavaScript. Do not depend on a backend.
- Important states should be reviewable inside the preview itself: loading, empty vs filled, drill-down detail, tab switches, and one or two key CTA transitions.
- The notes panel should auto-switch with the active screen and save edits to
localStorage. - Resizable vertical dividers between columns are allowed and may be enabled by default.
-
Build or update
figma_capture_index.htmlwhen the prototype may be captured into Figma. That page should fetch/index.html, parse the source HTML, clone the preview device once per screen, disable motion, and render one static section perdata-screen. Mark readiness withdocument.body.dataset.captureReady = "true".
What ships with it
6 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.
- 4d ago First seen · 81 lines · 88 tokens per session scan A 9eb9c8d7984f
prototype-previewer is a skill published in the GitHub repository chocpink123/prototype-previewer-skill (28 stars, last pushed 4mo ago), licensed MIT. It adds 88 tokens to every session and 1,024 once invoked, about $0.0004 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-30.
Other skills, from other repositories
hallmark
Anti-AI-slop design skill for greenfield pages, audits, redesigns, and design extraction from URLs or screenshots. Use when the user asks to build a new app or landing page, wants to redesign something, invokes Hallmark by name, or uses audit/redesign/study.
read
Reads URLs and PDFs by fetching source content, defaulting to concise summaries for plain read requests and clean Markdown when asked to convert, save, quote, cite, or feed downstream work. Use when users ask in any language to read, fetch, check, summarize, quote, cite, convert, or save a URL or PDF. Not for local…
accessibility
Consolidated accessibility skill entrypoint for WCAG 2.2, ARIA Authoring Practices, cognitive accessibility, Section 508, EN 301 549, design intent verification, and the Accessibility Planner workflow.
desktop-principles
Desktop-specific UX principles - hover states, pointer precision, keyboard shortcuts, multi-window, focus management. Covers macOS, Windows, Linux, web desktop.
taiyi-ui-design
TaiyiForge 第 4 阶段 — UI/UX 契约，产出 UI-DESIGN.md。四端通用。.
accessibility-analysis
服務可達性分析工具箱（accessibility / service coverage）。當用戶說「30km 路網可達」「最近 X 站」「服務範圍」「沙漠」「孤島」「等時圈」「isochrone」「可達性分析」「路網覆蓋」或要新增任何「離 POI 多遠」類型的分析時觸發。整合 mini-taiwan-pulse + taipei-gis-analytics 兩端 SOP，覆蓋三種視覺模式（路網染色 / Polygon 沿路網 / Hex 格點）、三套既有 reference pipeline 對照、模式選擇決策樹、常見坑（Overpass mirror 不穩 / pyrosm 爆 RAM / multi-bucket /…