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 oyusypenko/creo --skill creo-design-implementgit clone --depth 1 https://github.com/oyusypenko/creoWrote 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/oyusypenko/creo/creo-design-implement)<a href="https://agentmods.dev/skills/oyusypenko/creo/creo-design-implement"><img src="https://agentmods.dev/badge/skills/oyusypenko/creo/creo-design-implement/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/oyusypenko/creo/creo-design-implement"><img src="https://agentmods.dev/badge/skills/oyusypenko/creo/creo-design-implement.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.00052 | $0.01207 |
| Opus 5 | $0.00026 | $0.00603 |
| Sonnet 5 | $0.00010 | $0.00241 |
| Haiku 4.5 | $0.00005 | $0.00121 |
Grade A, and why
creo-design-implement 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 10d 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 — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design Implementation
Systematically execute implementation roadmaps created by creo-design-review. Works in iterative cycles, implementing fixes and verifying them through live browser testing until all design issues are resolved.
Commands
| Command | Description |
|---|---|
/creo design-implement <report-path> |
Execute fixes from a specific review report |
/creo design-implement auto |
Find the latest review report and implement fixes |
Core Instructions
Configuration
- Check for project-specific config at
.claude/project-config.md - Read
dev_server_url(default:http://localhost:3000),ui_framework,ui_rules,reports_path - Load project extension if it exists at
.claude/skills/creo-design-implement/creo-design-implement-{project_id}.md. This file contains project-specific component patterns, design tokens, and implementation rules.{project_id}comes fromproject-config.md. Always load it before doing work. - If no config exists, use defaults or ask user
Mobile-First Approach (Critical)
Check layout at sizes 375px, 768px, 1440px, 1920px. Start with 375px and work upward. For each viewport, make changes until the design is consistent and polished before moving to the next.
Mobile Layout Requirements (Mandatory)
Mobile (375px) Critical Issues
- Text Overflow: Headers and text must not exceed screen boundaries
- Button Sizes: Buttons must fit in viewport and be accessible for tapping
- Horizontal Scrolling: There should never be horizontal scrolling
- Touch Targets: Minimum 44px for all clickable elements
- Text Readability: Fonts must be readable (minimum 14px on mobile)
Typography Responsive Rules
- H1: 2rem on mobile, 3rem on desktop
- H2: 1.5rem on mobile, 2.25rem on desktop
- Body: 0.875rem on mobile, 1rem on desktop
- Buttons: 0.875rem on mobile, 1rem on desktop
Spacing Mobile Rules
- Container Padding: minimum 16px on each side on mobile
- Section Spacing: 32px between sections on mobile
- Component Spacing: 16px between components on mobile
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.
- 10d ago First seen · 147 lines · 52 tokens per session scan A accba98bad9f
creo-design-implement is a skill published in the GitHub repository oyusypenko/creo (4 stars, last pushed yesterday), licensed MIT. It adds 52 tokens to every session and 1,207 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
claude-design-patterns
Engineering rules and reusable patterns for building polished web UI, React artifacts, slide decks, animations, and device mockups — distilled from Anthropic's leaked Claude Design agent system prompt. Use ALONGSIDE the frontend-design skill whenever building or iterating on visual web output: single-file React/HTML…
frontend-design
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI).…
web-artifacts-builder
Suite of tools for creating elaborate, multi-component claude.ai 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.
html-artifacts
Author the HTML for a plan artifact, dashboard iframe, or Slack attachment — structure, design plan, available runtime, theming, and craft. Read this before writing HTML for saveplan, outputiframe, or slackattachhtml.
figma-implement-design
Translate Figma nodes into production-ready code with 1:1 visual fidelity using the Figma MCP workflow (design context, screenshots, assets, and project-convention translation). Trigger when the user provides Figma URLs or node IDs, or asks to implement designs or components that must match Figma specs. Requires a…
scroll-craft
Build premium scroll-driven landing pages for service, product, food, and drink brands. Plan the visitor journey, page grammar, emotional peak, and bespoke signature move. Create dimensional heroes with independent visual planes, restrained motion, and separate mobile composition. Use supplied photos and footage or…