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 DKeken/codex-skills-alternative --skill design-url-to-codegit clone --depth 1 https://github.com/DKeken/codex-skills-alternativeWrote 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/dkeken/codex-skills-alternative/design-url-to-code)<a href="https://agentmods.dev/skills/dkeken/codex-skills-alternative/design-url-to-code"><img src="https://agentmods.dev/badge/skills/dkeken/codex-skills-alternative/design-url-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/dkeken/codex-skills-alternative/design-url-to-code"><img src="https://agentmods.dev/badge/skills/dkeken/codex-skills-alternative/design-url-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.00099 | $0.01044 |
| Opus 5.5 | $0.00040 | $0.00418 |
| Sonnet 5.5 | $0.00020 | $0.00209 |
| Haiku 4.5 | $0.00010 | $0.00104 |
Grade A, and why
design-url-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 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design — URL To Code
Recreate a live site/page as an editable local frontend — faithful to the original and verified by comparison. Unlike image-to-code, you have the real HTML/CSS to extract from, so fidelity can be higher; the work is rebuilding it clean in your stack rather than copy-pasting markup.
When to use
- "Clone/rebuild this live site locally", "make it look like {url}".
- You want a real, editable starting point matching an existing site's design.
- Capturing a design language from a site you admire (legitimately — see rules).
When NOT to use
- The source is a static image/mockup, not a live URL →
design-image-to-code. - You need interactivity/flow wiring after →
design-prototype. - The goal is critique, not recreation →
design-audit.
Inputs
- Source URL(s).
- Target stack: ask; default match repo, else React + Vite + Tailwind + TS.
- Scope: full clone vs "capture the design language only".
Workflow
- Capture the page: open it in a browser-automation tool (DOM snapshot + full-page screenshot) and/or pull HTML/CSS via a web-fetch tool. The browser gives you computed styles; the screenshot is your comparison target.
- Extract the design system into
./design/url-dna.md: colors, type scale, spacing rhythm, layout structure, components, motion. Capture tokens, not pixel-by-pixel copies. - Rebuild locally in the target stack with your own clean components — not pasted markup. Map extracted tokens → real config (e.g. Tailwind theme extension).
- Verify: run locally, screenshot at the source's viewport, compare to the original; iterate to close gaps (layout → type → spacing → color).
- Assets: download/extract where permitted; generate missing raster with an image tool; placeholder otherwise.
Worked example
source: https://example.com/landing stack: React+Vite+Tailwind+TS
capture: browser snapshot (computed CSS) + full-page screenshot
url-dna.md:
palette: bg #0B0B0F, text #E7E7EA, accent #6366F1
type: Inter; scale 14/16/20/32/56; tight tracking on display
spacing: 4px base, section pad 96px
layout: sticky nav, hero (h1 + sub + 2 CTAs), 3-col feature grid, footer
motion: fade-up on scroll
rebuild: Tailwind theme = those tokens; components Nav/Hero/FeatureGrid/Footer
verify: screenshot @1440 vs original → hero h1 was 48 not 56, fixed; gap close
done: build clean, tokens in tailwind.config, runs at :5173
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 · 67 lines · 99 tokens per session scan A 1e335ff2e8ee
design-url-to-code is a skill published in the GitHub repository DKeken/codex-skills-alternative (15 stars, last pushed 4mo ago), licensed MIT. It adds 99 tokens to every session and 1,044 once invoked, about $0.0004 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-30.
Other skills, from other repositories
create-chatgpt-mockup
Render pixel-accurate ChatGPT mobile (iOS) screen mockups in light mode from a thread JSON. Supports user text bubbles, user image attachments, assistant markdown prose, citation chips, the OpenAI spiral logo, the Apps-SDK GPT chip in the composer, and three header styles (model-tag, plain title, "Get Plus"). Fixed…
vercel-composition-patterns
React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.
design-review
Five-dimension design audit (frontend UI/UX · server data-model & flow · endpoint spec · daemon-runtime/SDK & local-cache-first · built-in skill/agent-role), executed by a NON-implementing agent. Every dimension gets a verdict; N/A only with a stated reason. A dimension the design silently skipped must be surfaced as…
web-artifacts-builder
Suite of tools for creating elaborate, multi-component Prismer HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.
logo-generator
Deprecated compatibility entry for Logo construction. This component is now maintained in Bricks; install and use component-builder to build a new Logo.
popup-generator
Deprecated compatibility entry for Modal construction. This component is now maintained in Bricks; install and use component-builder to build a new Modal.