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 DKeken/codex-skills-alternative --skill product-designgit clone --depth 1 https://github.com/DKeken/codex-skills-alternativeWrote 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/dkeken/codex-skills-alternative/product-design)<a href="https://agentmods.dev/skills/dkeken/codex-skills-alternative/product-design"><img src="https://agentmods.dev/badge/skills/dkeken/codex-skills-alternative/product-design/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/dkeken/codex-skills-alternative/product-design"><img src="https://agentmods.dev/badge/skills/dkeken/codex-skills-alternative/product-design.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.00113 | $0.01152 |
| Opus 5 | $0.00056 | $0.00576 |
| Sonnet 5 | $0.00023 | $0.00230 |
| Haiku 4.5 | $0.00011 | $0.00115 |
Grade A, and why
product-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 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product Design — Orchestrator
The umbrella for the 9 design-* skills. Your job: read the request, locate it in the design process, route to the right sub-skill. Don't do the work here — dispatch. You're the design lead sequencing the work, not the IC executing each step.
When to use
- The user gives a broad design goal ("design a UI for X", "prototype this idea") and the step is ambiguous.
- A design project spans multiple stages and needs sequencing.
- The user doesn't know which sub-skill they need.
When NOT to use
- The user named a step explicitly ("audit this screen") → go straight to that sub-skill.
- It's visual-asset creation (ads, product shots, moodboards), not UI/UX →
creative-productionorchestrator.
The pipeline
FRAME EXPLORE BUILD SHIP
design-get-context ─► design-research ──► design-ideate ─► design-image-to-code ─┐
design-audit design-url-to-code ├─► design-prototype ─► design-qa ─► design-share
Frame the problem → explore options → build the chosen one → gate quality → ship for review.
Routing table
| User intent / phrasing | Route to |
|---|---|
| new design task, brief unclear | design-get-context (almost always start here) |
| "how do others do X", competitor/pattern scan | design-research |
| "what's wrong with this UI", review existing | design-audit |
| "give me layout options/directions" | design-ideate |
| "build this mockup/screenshot" | design-image-to-code |
| "clone/rebuild this live site" | design-url-to-code |
| "make it clickable", "wire the flow" | design-prototype |
| "does it match the design/spec" | design-qa |
| "share it", "give me a link", "publish" | design-share |
How to orchestrate
- Frame first. Unless
./design/context.mdalready exists, start withdesign-get-context. The cheapest fix is the question asked before building. - Explore with
research/auditas needed, thenideatedirections. - Build: turn the chosen direction into code via
image-to-code(from a mockup) orurl-to-code(from a live site), thenprototypeto wire interactivity. - Gate with
design-qabeforedesign-share. Don't ship HIGH-severity drift. context.mdis the shared source of truth — every sub-skill reads it; keep it current.
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 · 76 lines · 113 tokens per session scan A ba831df3114d
product-design is a skill published in the GitHub repository DKeken/codex-skills-alternative (15 stars, last pushed 3mo ago), licensed MIT. It adds 113 tokens to every session and 1,152 once invoked, about $0.0006 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
create-chatgpt-mockup
Render pixel-accurate ChatGPT mobile (iOS) screen mockups in light mode from a thread JSON. Supports user text bubbles, user image attachments, assistant markdown prose, citation chips, the OpenAI spiral logo, the Apps-SDK GPT chip in the composer, and three header styles (model-tag, plain title, "Get Plus"). Fixed…
vercel-composition-patterns
React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.
ui-designer/design-system
A shared set of rules for a product’s visual design, covering colors, fonts, spacing, corner shapes, shadows, and animations.
layout-skill
Layer A layout-mechanics reference. Stacks on any style skill when the screen is an app shell, dashboard, settings, list-detail, mail/inbox, or any layout with fixed regions plus a scrolling body — or when a layout breaks under long, empty, or unbroken content. Owns spatial structure and scroll ownership; owns zero…
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.
baoyu-design
Create polished design artifacts as self-contained HTML: UI mockups, interactive prototypes, wireframes, landing pages, dashboards, app screens, mobile apps, slide decks (a.k.a. PPT / PowerPoint presentations), documents and résumés, animations, 3D objects, research reports, HTML email, diagrams, fliers, and visual…