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/kayforkind/reimagine-it/extractnpx skills add Kayforkind/reimagine-it --skill extractgit clone --depth 1 https://github.com/Kayforkind/reimagine-itWrote 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/kayforkind/reimagine-it/extract)<a href="https://agentmods.dev/skills/kayforkind/reimagine-it/extract"><img src="https://agentmods.dev/badge/skills/kayforkind/reimagine-it/extract.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.1 | $0.00133 | $0.00897 |
| Opus 5 | $0.00067 | $0.00449 |
| Sonnet 5 | $0.00027 | $0.00179 |
| Haiku 4.5 | $0.00013 | $0.00090 |
Grade A, and why
reimagine-it-extract 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 yesterday.
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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/reimagine-it extract
Parent: ../SKILL.md — the full Content-Derived Design engine. This sub-skill handles only the extraction surface — the honesty layer the whole method stands on.
The redesign is only as honest as its extraction. This verb emits exactly what the engine reads, as JSON, without generating anything: title, profile, density, derived palette, anchors, proper nouns, headings, dates, numbers, emails, links, and source hex colors. Every extracted fact exists in the source — property-tested against hostile and malformed input.
Usage
npx reimagine-it extract -i page.html -o signals.json
cat page.html | npx reimagine-it extract -o - # stdin → stdout
npx reimagine-it extract -i page.html --full -o signals.json # + prose
Payload shape (default):
{
"source": "page.html",
"title": "…",
"profile": "restaurant | saas | civic | …",
"density": "sparse | medium | dense",
"palette": { "ground": "…", "accent": "…", "muted": "…", "surface": "…", "ink": "…" },
"anchors": ["…"],
"properNouns": ["…"],
"headings": ["…"],
"dates": ["…"],
"numbers": ["…"],
"emails": ["…"],
"links": ["…"],
"sourceHex": ["#6B3A2A"],
"counts": { "paragraphs": 4, "listItems": 16 }
}
--full adds paragraphs and items (the raw prose arrays).
Procedure
- Run it before any redesign when the user asks "what would you even use from this page?" — the JSON answers with the engine's actual inputs.
- To audit honesty: every
dates,numbers,emails, andlinksentry must be findable in the source. Nothing else is allowed to appear. - Use it for migration/research: the payload is a stable, typed summary of a page's content — no redesign attached.
Must not
- Add facts not present in the payload to any downstream summary
- Present the derived
paletteas colors the source declared — hex colors insourceHexwere in the source; the rest is derivation - Round or "clean up" extracted numbers and dates; they are quotes
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.
- yesterday First seen · 100 lines · 133 tokens per session scan A bf592e8a3aeb
reimagine-it-extract is a skill published in the GitHub repository Kayforkind/reimagine-it (37 stars, last pushed yesterday), licensed MIT. It adds 133 tokens to every session and 897 once invoked, about $0.0007 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-09-05.
Other skills, from other repositories
popular-web-designs
54 real design systems (Stripe, Linear, Vercel) as HTML/CSS.
21st-ui
Find, install, and generate UI with 21st.dev. Use when the user asks for a UI component (pricing table, hero, navbar, dashboard, form, etc.), wants design inspiration, needs a brand logo as an SVG component, or wants to generate new UI from a prompt.
interaction-skill
Layer A interaction-mechanics reference anchored to the beui.dev catalog. Stacks on any style skill whenever work adds or changes motion or interaction — micro-interactions, animated components, transitions, gestures, hover/press/state feedback, loading/success/error morphs, 'make it feel alive'. Mandates reading the…
layout-skill
Layer A layout-mechanics reference. Stacks on any style skill when the screen is an app shell, dashboard, settings, list-detail, mail/inbox, or any layout with fixed regions plus a scrolling body — or when a layout breaks under long, empty, or unbroken content. Owns spatial structure and scroll ownership; owns zero…
refero-design
Primary/default skill for UI design, product design, web design, landing pages, dashboards, product screens, redesigns, visual polish, frontend/CSS styling, design systems, components, responsive design, typography, color, spacing, motion, icons, accessibility, copywriting, conversion, and anti-AI-slop work. Use this…
taste-skill
Anti-slop frontend skill for landing pages, portfolios, and redesigns. The agent reads the brief, infers the right design direction, and ships interfaces that do not look templated. Real design systems when applicable, audit-first on redesigns, strict pre-flight check.