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/first-fluke/fullstack-starter/oma-designnpx skills add first-fluke/fullstack-starter --skill oma-designgit clone --depth 1 https://github.com/first-fluke/fullstack-starterWrote 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/first-fluke/fullstack-starter/oma-design)<a href="https://agentmods.dev/skills/first-fluke/fullstack-starter/oma-design"><img src="https://agentmods.dev/badge/skills/first-fluke/fullstack-starter/oma-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 | $0.00058 | $0.03207 |
| Opus 5 | $0.00029 | $0.01604 |
| Sonnet 5 | $0.00012 | $0.00641 |
| Haiku 4.5 | $0.00006 | $0.00321 |
Grade A, and why
oma-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 today.
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 oma-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.
How it starts
The opening of the file, as written. The whole thing — 276 lines — stays where its author put it; the contents beside it link to each section on GitHub.
oma-design
Scheduling
Goal
Design specialist that defines, creates, and validates project design systems. DESIGN.md is the central artifact; all design work revolves around it.
Intent signature
- User asks for design system,
DESIGN.md, visual direction, typography, color, motion, accessibility, anti-pattern review, or component guidance. - User needs design decisions before frontend implementation or wants UI quality audited from a design perspective.
When to use
- Defining or revising a project design system
- Creating or auditing
DESIGN.md - Selecting typography, color, layout, motion, or component direction
- Reviewing UI work for responsive behavior, accessibility, and visual quality
- Redesigning an existing site or app (preserve vs overhaul modes)
- Using optional vendor inspiration from Stitch MCP or getdesign
When NOT to use
- Implementing frontend components or application UI -> use
oma-frontend - Planning product scope or task breakdown -> use
oma-pm - Backend, database, infrastructure, or mobile implementation -> use the relevant specialist skill
- General quality/security review outside visual, interaction, and accessibility concerns -> use
oma-qa
Expected inputs
- Product, brand, audience, platform, and UI/design problem
- Existing
.design-context.md,DESIGN.md, screenshots, references, or component constraints - Accessibility, responsive, language, and implementation constraints
Expected outputs
- Design direction, revised
DESIGN.md, audit findings, component guidance, or handoff notes - Responsive-first, WCAG-aware design recommendations
- Optional vendor seed attribution when getdesign is used
outputs:
- name: design-doc
description: Updated DESIGN.md when the run materially advances the design system
artifact: "DESIGN.md"
required: false
- name: design-context
description: Refreshed .design-context.md snapshot when a discovery pass runs
artifact: ".design-context.md"
required: false
What ships with it
22 files 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.
- examples/design-context-example.md 3.0 KB
- examples/landing-page-prompt.md 4.8 KB
- reference/accessibility.md 4.4 KB
- reference/color-and-contrast.md 3.7 KB
- reference/component-patterns.md 5.7 KB
- reference/motion-design.md 7.9 KB
- reference/responsive-design.md 3.6 KB
- reference/shader-and-3d.md 5.0 KB
- reference/spatial-design.md 2.8 KB
- reference/typography.md 2.6 KB
- reference/visual-hierarchy.md 9.6 KB
- resources/anti-patterns.md 8.4 KB
- resources/asset-strategy.md 3.0 KB
- resources/checklist.md 5.6 KB
- resources/design-md-spec.md 8.3 KB
- resources/design-tokens.md 3.9 KB
- resources/error-playbook.md 3.9 KB
- resources/execution-protocol.md 14 KB
- resources/getdesign-fetcher.md 13 KB
- resources/prompt-enhancement.md 9.2 KB
- resources/redesign-protocol.md 3.7 KB
- resources/stitch-integration.md 3.8 KB
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.
- today First seen · 276 lines · 58 tokens per session scan A 9bfbb957cbb1
oma-design is a skill published in the GitHub repository first-fluke/fullstack-starter (222 stars, last pushed today), licensed MIT. It adds 58 tokens to every session and 3,207 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 oma-design, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
kiranism-shadcn-dashboard
Guide for building features, pages, tables, forms, themes, and navigation in this Next.js 16 shadcn dashboard template. Use this skill whenever the user wants to add a new page, create a feature module, build a data table, add a form, configure navigation items, add a theme, set up RBAC access control, or work with…
omd:landing
Scroll-native one-page landing that overwhelms — concept, composition, asset placement, and scroll choreography derived from DESIGN.md and the measured landing-craft codex. Trigger: '랜딩 페이지', '원페이지', 'landing page', 'one-pager', 'hero to footer', '스크롤 랜딩', 'affinity.studio 같은'.
omd:aphrodite
Maximum-craft one-page landing — the wow bar. omd:landing 의 구조 위에 마감(서체 조달·그레인·깊이·색보정·스크롤 타임라인)과 최고급 에셋을 얹고, 랜딩 검사 전 항목 통과를 합격선으로 삼는다. Trigger: '와우', '압도적인', '최고급', '쇼케이스용', 'aphrodite', '데모용 랜딩', '이거 자랑할 거야'.
playwright-testing
Use when writing Playwright tests, fixing flaky tests, debugging failures, implementing Page Object Model, configuring CI/CD, optimizing performance, mocking APIs, handling authentication or OAuth, testing accessibility (axe-core), file uploads/downloads, date/time mocking, WebSockets, geolocation, permissions…
frontend-design
Build distinctive, production-quality UI. Use when creating or reshaping user-facing interfaces, components, pages, layouts, visual redesigns, responsive behavior, loading/error/empty states, or accessibility-sensitive frontend work.
system-architecture
Design systems with appropriate complexity - no more, no less. Use when the user asks to architect applications, design system boundaries, plan service decomposition, evaluate monolith vs microservices, make scaling decisions, or review structural trade-offs. Applies to new system design, refactoring, and migration…