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/openclaw/carapace/openclaw-designnpx skills add openclaw/carapace --skill openclaw-designgit clone --depth 1 https://github.com/openclaw/carapaceWrote 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/openclaw/carapace/openclaw-design)<a href="https://agentmods.dev/skills/openclaw/carapace/openclaw-design"><img src="https://agentmods.dev/badge/skills/openclaw/carapace/openclaw-design.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.00058 | $0.00445 |
| Opus 5 | $0.00029 | $0.00222 |
| Sonnet 5 | $0.00012 | $0.00089 |
| Haiku 4.5 | $0.00006 | $0.00044 |
Grade A, and why
openclaw-design 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.
This is a copy
100% identical to openclaw-design — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
OpenClaw Design
Choose one focused branch before changing an interface. Load multiple branches only when the task genuinely crosses them.
| Skill | Use for |
|---|---|
openclaw-brand |
Identity decisions, typography, logos, imagery, voice, and non-product brand artifacts |
openclaw-carapace |
Application UI, semantic tokens, themes, component reuse, and framework adapters |
openclaw-design-system |
Compatibility alias for projects upgrading an existing skill lock |
openclaw-marketing-pages |
Public-page composition, landing/content pages, navigation, SEO, and responsive layout |
openclaw-design-audit |
Design drift, token misuse, component substitution, accessibility, and recurring audits |
For a public website change, start with openclaw-marketing-pages and add
openclaw-brand only when the task changes identity, logo, imagery, typography,
or voice. For a product application, start with openclaw-carapace when it is
installed. Projects upgrading an existing lock may use
openclaw-design-system as the v0.1.x compatibility alias.
Shared Contract
- Install agent guidance from this repository's default branch and refresh it with
npx [email protected] update --project --yes. - Keep runtime CSS pinned to a semantic release tag.
- Prefer semantic tokens over raw palette values.
- Keep product-specific components and layouts in their consumer repository.
- Add shared implementation only after at least two consumers demonstrate the same interface.
- Preserve consumer behavior while changing the visual foundation.
- Validate rendered pages in a real browser at desktop and mobile sizes.
- Check both light and dark themes where the consumer supports them.
- Do not redistribute fonts, logos, or artwork without recorded permission.
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 · 37 lines · 58 tokens per session scan A 6814c86e4328
openclaw-design is a skill published in the GitHub repository openclaw/carapace (4 stars, last pushed 3d ago), licensed MIT. It adds 58 tokens to every session and 445 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to openclaw-design, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
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…
preline-mcp
Add, integrate, or build Preline UI components and blocks into HTML files via the Preline MCP server. Use when the user mentions "preline", says "/preline", asks to add a UI component, or requests a Preline block (a ready-made page section) using Preline UI.
preline-theme-generator
Generate, preview, save, or validate Preline theme CSS using the bundled local generator in this skill. Use when the user asks to create a new Preline theme, match a brand color, translate a mood into a theme, generate light and dark theme CSS, preview theme output without writing files, or review and fix generated…
tailwindcss-docs
Comprehensive Tailwind CSS v4 reference covering installation, all utility classes, responsive design, dark mode, customization, and advanced patterns. Use whenever the user mentions Tailwind CSS, utility classes, styling components, responsive layouts, custom themes, or needs help with any Tailwind-specific code…
popular-web-designs
54 real design systems (Stripe, Linear, Vercel) as HTML/CSS.
magic-ui
Use this skill when users want to add, customize, or troubleshoot Magic UI components in React/Next.js projects. It covers component selection, shadcn registry installation (@magicui/), integration patterns, and practical quality checks for accessibility and maintainability.