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 gracefullight/docusaurus-plugins --skill oma-designgit clone --depth 1 https://github.com/gracefullight/docusaurus-pluginsWrote 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/gracefullight/docusaurus-plugins/oma-design)<a href="https://agentmods.dev/skills/gracefullight/docusaurus-plugins/oma-design"><img src="https://agentmods.dev/badge/skills/gracefullight/docusaurus-plugins/oma-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/gracefullight/docusaurus-plugins/oma-design"><img src="https://agentmods.dev/badge/skills/gracefullight/docusaurus-plugins/oma-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.00058 | $0.02729 |
| Opus 5.5 | $0.00023 | $0.01092 |
| Sonnet 5.5 | $0.00012 | $0.00546 |
| Haiku 4.5 | $0.00006 | $0.00273 |
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 1mo 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.
This is a copy
88% identical to oma-design — 155 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 — 260 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
- 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
Dependencies
.design-context.mdandDESIGN.md- Design resources, references, anti-pattern catalog, and optional Stitch/getdesign integrations
- shadcn/component library context when recommending components
What ships with it
20 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 4.0 KB
- resources/checklist.md 2.9 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 9.2 KB
- resources/getdesign-fetcher.md 13 KB
- resources/prompt-enhancement.md 4.4 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.
- 1mo ago First seen · 260 lines · 58 tokens per session scan A bebf85ff0010
oma-design is a skill published in the GitHub repository gracefullight/docusaurus-plugins (23 stars, last pushed 27d ago), licensed MIT. It adds 58 tokens to every session and 2,729 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 88% identical to oma-design, differing in 155 lines, and is treated as a copy.
Other skills, from other repositories
cometchat-react-v7-customization
Theme and brand the React v7 UI Kit — light/dark mode, CSS custom-property design tokens, per-component style overrides. Triggers: 'change chat colors', 'dark mode chat', 'match my brand', 'customize cometchat theme', 'override message list styles'.
cometchat-angular-v5-customization
Brand and customize the CometChat Angular UI Kit — CSS variable tokens, light/dark via ThemeService, localization, date/time formats, global config, and swapping component regions with ng-template. Triggers: 'change the chat colours', 'match my brand angular', 'dark mode', 'translate the chat', 'change the date…
UI Designer
React + TypeScript + Tailwind CSS chat interface specialist for this project's streaming chat UI.
chakra-ui-builder
Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…
visual-ralph
Visual Ralph orchestration for frontend UI from generated references, static references, or live URL targets, using $ultragoal with built-in visual verdict and pixel-diff evidence until the implementation matches and leaves a reproducible design system.
frontend-ui-dark-ts
Build dark-themed React applications using Tailwind CSS with custom theming, glassmorphism effects, and Framer Motion animations. Use when creating dashboards, admin panels, or data-rich interfaces with a refined dark aesthetic.