Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/firecrawl/firecrawl-workflowsnpx agentmods add skills/firecrawl/firecrawl-workflows/firecrawl-website-design-cloneWrote 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/firecrawl/firecrawl-workflows/firecrawl-website-design-clone)<a href="https://agentmods.dev/skills/firecrawl/firecrawl-workflows/firecrawl-website-design-clone"><img src="https://agentmods.dev/badge/skills/firecrawl/firecrawl-workflows/firecrawl-website-design-clone.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.00069 | $0.01651 |
| Opus 5 | $0.00034 | $0.00826 |
| Sonnet 5 | $0.00014 | $0.00330 |
| Haiku 4.5 | $0.00007 | $0.00165 |
Grade A, and why
firecrawl-website-design-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 6d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- firecrawl-website-design-clone — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Firecrawl Website Design Clone
Use this when the user wants one URL turned into a practical design system file agents can use immediately.
Default outcome: extract any website's design system in one line and format it as DESIGN.md.
The skill should feel like a thin workflow around Firecrawl scrape: gather the page's visible content, structure, metadata, links, and available visual signals, then synthesize those findings into a clean design-system markdown file.
Onboarding Interview
Infer the source URL, target stack, and whether implementation is requested from context. If the user gives a URL and asks for a design system, proceed immediately.
Ask at most 1-3 concise questions only if blocked, such as the website URL, whether to output only DESIGN.md or also implement, or a required target stack.
Use the host agent's normal prompt or modal UI. Do not name a harness-specific question function.
Firecrawl Collection Plan
Use Firecrawl through the CLI or equivalent tool surface. Always start with two parallel scrapes of the supplied URL:
- The
brandingandimagesformats together for structured design tokens and the full set of page images. - A full-page screenshot for visual context.
Example:
firecrawl scrape "https://example.com" --format branding,images -o ".firecrawl/example-branding.json" --pretty &
firecrawl scrape "https://example.com" --full-page-screenshot -o ".firecrawl/example-screenshot.png" &
wait
Combining branding and images in one call still costs a single credit and is required: the branding block only surfaces curated brand assets (logo, favicon, ogImage, logoHref), so without images the agent will miss the page's actual content imagery (heroes, product shots, carousel slides, feature visuals, illustrations, accessory photos, end-of-page artwork, and similar). On a product page like tesla.com/cybertruck the branding block has no hero — only images returns the main Cybertruck hero (e.g. Cybertruck-Hero-Desktop-NA-SA-APAC.png) and the rest of the page's photography.
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.
- 6d ago First seen · 145 lines · 69 tokens per session scan A 94b1beac1027
firecrawl-website-design-clone is a skill published in the GitHub repository firecrawl/firecrawl-workflows (151 stars, last pushed 16d ago), licensed ISC. It adds 69 tokens to every session and 1,651 once invoked, about $0.0003 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
figma-to-webui
Recreate Figma design frames as production-ready Chromium WebUI code following Chrome's Lit-element architecture and styling guidelines. Use when asked to create WebUI code from a Figma frame URL.
generate-component-spec
Maps a Figma component from the Chrome Design System (CDS) to equivalent C++ Views, WebUI, and Clank (Android) components in the Chromium codebase. Generates a comprehensive side-by-side comparative Markdown specification detailing layout variants, interactive states, design tokens, architectural and implementation…
generate-token-map
Maps all Figma design tokens from figma-variables.md to their equivalent C++ (Views) identifiers, CSS (WebUI) variables, and Clank (Android) resource attributes/macros/methods in Chromium, and saves the formatted mapping table to the assets directory of the Chrome Design System project. Use this skill when asked to…
figma-to-views
Recreate Figma design frames as production-ready Chromium C++ Views code following Chrome's native Views architecture, component guidelines, and color/shape token mappings. Use when asked to create C++ Views code from a Figma frame URL.
browserwing-executor
Control browser automation through HTTP API. Supports page navigation, element interaction (click, type, select), data extraction, accessibility snapshot analysis, screenshot, JavaScript execution, and batch operations.
figma-design-review
Critique and review Figma designs to ensure alignment with Chromium codebase components, tokens, and structure. Use when the user asks to critique, review, or audit a design, check alignment with code, or compare a Figma node against component specifications or coding standards.