clone

A command for studying an existing website and extracting its visual design rules into a clean prototype design system. It examines rendered styles and font declarations while leaving the original layout and wording out.

In plain words
What is it for?
Use it to reverse-engineer colors, typography, and other design tokens from a website reference, then use them in a code-based prototype.
Why use it?
It reduces guesswork when recreating a site's visual identity. It also asks you to confirm the extracted design settings before treating them as final.

Command for Codex

Install

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.

agentmods
npx agentmods add commands/alwkala/tidyfactor-design/clone
Clone the repo
git clone --depth 1 https://github.com/alwkala/tidyfactor-design

Made for: Codex.

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 347 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00347
Opus 5 $0.00000 $0.00173
Sonnet 5 $0.00000 $0.00069
Haiku 4.5 $0.00000 $0.00035

Measured 2d ago against content hash 857435547414, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

clone 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 2d 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.

.agents/skills/tidyfactor-design/references/commands/clone.md · 27 lines

What it actually says

Command: clone — Reverse-Engineering & Design System Extraction

Runtime entry point for reverse-engineering an external website reference into a clean, code-native prototype design system.

Computed-Style Extraction Protocol

When reverse-engineering an existing brand reference:

  1. Computed Styles: Sample actual rendered hex values from getComputedStyle() on key DOM elements (buttons, headers, body text) rather than visual guesses from screenshots.
  2. Typography Declarations: Read exact font family names from <link> tags and @font-face declarations.
  3. Draft Confirmation: Always present extracted brand.json v2 drafts back to the user for explicit confirmation before writing as final.
  4. Token Isolation: Extract design system tokens ONLY — do not carry over source layout structure or literal copy text.

Dispatch Steps

  1. Load references/memory/architecture.md — locked file tree layout and consistency rules.
  2. Load memory/03-narrative-conversion.md — token derivation rules.
  3. Load references/workflows/clone-prototype.md — execution sequence, multi-state diffing, and validation checklist.
  4. Enforce 150-Line Complexity Budget Rule: split sections exceeding 150-line specs into sub-component tasks.
  5. Execute workflow steps per clone-prototype.md.

Checklist

  • Interaction models (scroll-driven, click-driven, hover-driven) documented before building
  • Multi-state CSS transition diffs mapped to tokens.css
  • Component specs written to docs/research/components/
  • references/workflows/clone-prototype.md validation checklist fully satisfied
Changes

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.

  1. 2d ago First seen · 27 lines · 0 tokens per session scan A 857435547414

Subscribe to this mod's changes

clone is a command published in the GitHub repository alwkala/tidyfactor-design (5 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 347 tokens. 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.