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/leefanv/omit-design/omit-design-clinpx skills add leefanv/omit-design --skill omit-design-cligit 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/omit-design-cli)<a href="https://agentmods.dev/skills/leefanv/omit-design/omit-design-cli"><img src="https://agentmods.dev/badge/skills/leefanv/omit-design/omit-design-cli.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.00060 | $0.00549 |
| Opus 5 | $0.00030 | $0.00275 |
| Sonnet 5 | $0.00012 | $0.00110 |
| Haiku 4.5 | $0.00006 | $0.00055 |
Grade A, and why
omit-design-cli 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 5d 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
omit-design-cli
The entry points for the omit-design dev loop. Use these three commands — do not stitch together your own shell substitute.
omit-design init <name>
Scaffold a new omit-design project.
- Copies the init scaffold into
./<name>/. - Already includes:
app/(Vite shell),design/welcome.tsx(demo),mock/,preset/,.claude/skills/(bundled — no need fornpx skills add),eslint.config.js,vite.config.ts,tsconfig.json,CLAUDE.md,README.md. - Next:
cd <name> && npm install && npm run dev.
Flags:
--force: overwrite even if the target directory exists and is non-empty (use with care).
omit-design dev
Start the local Vite dev server.
- Default port 5173.
- Spawns
npx vite, inheriting stdio. Ctrl+Cto exit.
Flags:
--port <n>: change port.--host: expose on the LAN (use sparingly — designs may be visible to anyone on the same network).
omit-design lint
Compliance check. Produces AI-friendly structured output.
- Runs ESLint over
design/**/*.tsx(override with--glob). - Output format:
<emoji> [<rule-id>] <file>:<line>:<col> — <sample> → <hint>. - Exit code: violations → 1, clean → 0.
Flags:
--json: emit raw ESLint JSON (for tool consumption).--glob <pattern>: override the default glob.
Counter-examples
- Running
eslint design/...and parsing the output yourself — useomit-design lint. - Writing a
grepself-check forstyle={{—no-design-literalalready covers this. - Hard-coding the
devport in a README — users override it via--port.
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.
- 5d ago First seen · 54 lines · 60 tokens per session scan A 80b2360262d4
omit-design-cli is a skill published in the GitHub repository leefanv/omit-design (54 stars, last pushed 3mo ago), licensed MIT. It adds 60 tokens to every session and 549 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-30.
Other skills, from other repositories
nw-discuss
Conducts Jobs-to-be-Done analysis, UX journey design, and requirements gathering through interactive discovery. Use when starting feature analysis, defining user stories, or creating acceptance criteria.
nw-diverge
Generates 3-5 divergent design directions through JTBD analysis, competitive research, structured brainstorming, and taste evaluation before convergence. Use when the team has a validated problem but hasn't chosen a solution approach.
nw-fp-usable-design
Naming conventions, API ergonomics, and usability patterns for functional code.
moai-ref-ui-polish
UI polish and interface-completion reference: the small visual details — concentric border radius, optical alignment, shadow-vs-border, motion easing, typography smoothing, tabular numbers, icon stroke weight, hit areas — that separate polished interfaces from generic ones. Agent-extending skill that amplifies…
ux-design
Create comprehensive UX design with user flows, wireframes, and design systems.
moai-domain-design-dna
Reverse-engineer a reference design — a screenshot, an image set, or a live URL — into a portable Design DNA JSON across three dimensions (measurable tokens, qualitative style, special-rendering effects), then generate a new self-contained artifact from that JSON. Carries the extraction rules (dominance-based colour…