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 leefanv/omit-design --skill new-designgit clone --depth 1 https://github.com/leefanv/omit-designWrote 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/leefanv/omit-design/new-design)<a href="https://agentmods.dev/skills/leefanv/omit-design/new-design"><img src="https://agentmods.dev/badge/skills/leefanv/omit-design/new-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.00072 | $0.00903 |
| Opus 5 | $0.00036 | $0.00451 |
| Sonnet 5 | $0.00014 | $0.00181 |
| Haiku 4.5 | $0.00007 | $0.00090 |
Grade A, and why
new-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 8d 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
new-design — generate a design page from a PRD
When to trigger
- The user provides a PRD.
- The user says "make a design for the X page" / "add a design for X".
Decision tree (stop here — confirm pattern + whitelist before going further)
-
Find or create the matching pattern in
<project>/patterns/.- If
patterns/is empty:- User provided a PRD → invoke
/distill-patterns-from-prdfirst. Resume here only after files land and the user approves. - No PRD → invoke
/add-patternin conversational mode (it asks 3-5 clarifying questions and produces a minimal pattern). Resume here only after the user approves.
- User provided a PRD → invoke
- If
patterns/is non-empty:- Read each
<project>/patterns/<id>/README.mdand decide. If nothing fits → invoke/add-patternto create one. Surface the choice to the user before proceeding.
- Read each
- Never pick a pattern silently — the chosen pattern name must be confirmed in chat.
- If
-
All required components are on the preset Om whitelist* (exported from
@omit-design/preset-mobile). If a component is missing → stop. Either re-scope the pattern viaadd-pattern, or propose adding an upstreamOm*wrapper. Never bypass the whitelist by importing visual components directly from@ionic/react.
Execution flow
See references/checklist.md for the full 7-step checklist (read PRD / read patterns/ / check whitelist / prepare mock / copy template / self-check / verify).
The core point: step 5, "write the page," really means "copy <project>/patterns/<chosen>/template.tmpl.tsx and replace placeholders" — not write from scratch.
Delegate the mechanical work (when pattern-applier agent is present)
Once the HARD-GATE passes (pattern confirmed + whitelist verified) and the user has approved the chosen pattern + target path, delegate steps 5–7 (template copy → self-check → verify) to the pattern-applier sub-agent if .claude/agents/pattern-applier.md exists. This keeps the main conversation focused on user dialogue and prevents the template + lint-output from clogging context.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago First seen · 61 lines · 72 tokens per session scan A c565a4363911
new-design is a skill published in the GitHub repository leefanv/omit-design (54 stars, last pushed 3mo ago), licensed MIT. It adds 72 tokens to every session and 903 once invoked, about $0.0004 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
moai-design-tools
Design tool integration specialist covering Figma MCP, Pencil renderer, and Pencil-to-code export. Use when fetching design context from Figma, rendering Pencil designs, or exporting to React/Tailwind code.
moai-domain-uiux
UI/UX design systems specialist covering accessibility, icons, theming, design tokens, and user experience patterns. Use when working on design systems, WCAG compliance, ARIA patterns, or dark mode theming.
ux-design
Create comprehensive UX design with user flows, wireframes, and design systems.
premium-experience
Premium app generation that creates WOW-factor experiences. Multi-page apps with smooth animations, zero TypeScript errors, and production-ready quality. Lovable-style experience: one prompt, complete app, instant delight. MUST be used alongside vibe-orchestrator for new projects.
ui-first-builder
Creates production-ready UI immediately from any description. Generates complete pages, components, and realistic mock data in FIRST response. Uses Next.js 16 + Tailwind + shadcn/ui. Never asks questions - infers everything from context. Triggers: UI creation, page building, component generation, build interface…
agentic
Conversational AI-first interface with minimal controls, clear outcomes, and delegated task flows for agentic workflows.