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/darcos-loft/fluid/redesignnpx skills add Darcos-Loft/fluid --skill redesigngit clone --depth 1 https://github.com/Darcos-Loft/fluidWrote 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/darcos-loft/fluid/redesign)<a href="https://agentmods.dev/skills/darcos-loft/fluid/redesign"><img src="https://agentmods.dev/badge/skills/darcos-loft/fluid/redesign.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.00058 | $0.00490 |
| Opus 5 | $0.00029 | $0.00245 |
| Sonnet 5 | $0.00012 | $0.00098 |
| Haiku 4.5 | $0.00006 | $0.00049 |
Grade A, and why
redesign 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.
What it actually says
Redesign
Audit-first. For a site that already works but looks templated or dated, this finds what is wrong, decides what to keep, and ships a committed new identity, without throwing away working structure.
When to use
- An existing site (Webflow, WordPress, an old React app) needs to look current.
- A client hands you a live URL and wants it modernized.
- A redesign that must preserve content, SEO, and routes.
The workflow
- Audit. Run the
fluiddetector on the codebase (or read the live DOM and CSS). Catalogue the generic-look tells: fonts, palette, spacing, shadows, the slop list. Note what is genuinely good and worth keeping. - Draw the keep/change line. Preserve: content, information architecture, routes, anything that converts. Change: the identity (palette, type, surface, motion), the layout repetition, the bans.
- Generate the new identity with the
design-systemskill. Brief it from the brand, pick fromdata/, commit. Two redesigns in the same sector get different palettes. - Map old to new. A token migration: old hardcoded values become new CSS variables, component by component. Keep a small table so nothing is missed.
- Re-skin, do not rebuild. Keep the markup and structure, swap the look: tokens, type, motion. Add
fluidmotion where it earns its place. - Pre-flight. Run the detector again, check
design-system/reference/rules.md(locks, hero discipline, bans). Produce a before/after so the value is visible.
Rules
- Preserve what converts. A redesign that drops content or breaks routes is a rewrite, not a redesign.
- One identity, committed. Never half-redesign (new colors on old fonts).
- Show the before and after.
Pairs with: design-system (the new identity), fluid (the motion and the detector audit).
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 · 30 lines · 58 tokens per session scan A e77c70626a4c
redesign is a skill published in the GitHub repository Darcos-Loft/fluid (3 stars, last pushed 1mo ago), licensed MIT. It adds 58 tokens to every session and 490 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-31.
Other skills, from other repositories
extract-design
Extract the full design language from any website URL. Produces 8 output files including AI-optimized markdown, visual HTML preview, Tailwind config, React theme, shadcn/ui theme, Figma variables, W3C design tokens, and CSS variables. Also runs WCAG accessibility scoring. Use when user says 'extract design', 'get…
designlang-tokens
Use when styling UI for cal.com — references the extracted design system tokens instead of inventing colors, spacing, or typography.
morphous-catalog
Create or refresh Morphous website design-system/theme bundles from animal, insect, plant, landscape, mineral, weather, or other nature motifs. Use when Codex is asked to generate Morphous motif images, light/dark design-system boards, reusable image prompts, generated web assets, shadcn/tweakcn theme exports, or the…
brandmd
Extract a website's design system into a DESIGN.md file. Use when starting a new frontend project, rebuilding a site, or when the user wants AI-generated UI to match an existing brand.
Document Design Foundation
Shared design system, CSS standards, and operational workflow for all document generation skills.
google-fonts
Google Fonts typography system generator. Suggests single fonts (strict mode) and font pairs (contrast mode) with complete typographic scales following Tailwind Typography rhythm concepts. Generates CSS custom properties, Tailwind config, and embed links. Trigger: "choose a font", "font pairing", "typography system"…