oma-design

oma-design is a skill for Claude Code, Codex from first-fluke/fullstack-starter. It costs 32 tokens per session (1,754 once invoked), scanned A, a copy of oma-design, MIT.

A design-planning skill that defines a project's visual rules in a DESIGN.md file, including typography, colours, layouts, motion, components, and accessibility.

In plain words
What is it for?
Use it to create or review a design system, choose visual styles, assess responsive behaviour and accessibility, or guide a site or app redesign.
Why use it?
It gives frontend work a shared visual direction and helps catch inconsistent, hard-to-use, or inaccessible interface choices before implementation.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents).

Good fit Use it to create or review a design system, choose visual styles, assess responsive behaviour and accessibility, or guide a site or app redesign.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/first-fluke/fullstack-starter/oma-design
Install

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.

Any agent
npx skills add first-fluke/fullstack-starter --skill oma-design
Clone the repo
git clone --depth 1 https://github.com/first-fluke/fullstack-starter

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for oma-design

README.md
[![agentmods](https://agentmods.dev/badge/skills/first-fluke/fullstack-starter/oma-design/github.svg)](https://agentmods.dev/skills/first-fluke/fullstack-starter/oma-design)
Your own site
<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/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.

agentmods 80×15 button for oma-design

Your own site · 80×15
<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="Reviewed on agentmods" width="80" height="20"></a>
Per session 32 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,754 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00032 $0.01754
Opus 5.5 $0.00013 $0.00702
Sonnet 5.5 $0.00006 $0.00351
Haiku 4.5 $0.00003 $0.00175

Measured today against content hash 5286ce59e3f3, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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.

Origin

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.

.agents/skills/oma-design/SKILL.md · 159 lines

How it starts

The opening of the file, as written. The whole thing — 159 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

Read the full file on GitHub · 159 lines

Changes

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.

  1. today Changed 5286ce59e3f3
  2. 1mo ago Changed · -117 lines · -26 tokens per session ad45d53773b3
  3. 1mo ago First seen · 276 lines · 58 tokens per session scan A 9bfbb957cbb1

Subscribe to this mod's changes

oma-design is a skill published in the GitHub repository first-fluke/fullstack-starter (224 stars, last pushed yesterday), licensed MIT. It adds 32 tokens to every session and 1,754 once invoked, about $0.0001 per session on Opus 5.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.

Related

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…

Kiranism/next-shadcn-dashboard-starter · 142 tokens

common-architecture-diagramming

Draws architecture diagrams as editable draw.io files with a fixed house style, C4 levels, evidence-tagged shapes, and optional multi-view identity checks. Use when producing a system context, container, component, deployment, data flow, sequence, state, or ERD, or redrawing an ASCII or Mermaid one.

HoangNguyen0403/agent-skills-standard · 71 tokens

common-ui-design

Design distinctive, production-grade frontend UI with bold aesthetic choices. Use when building web components, pages, interfaces, dashboards, or applications in any framework (React, Next.js, Angular, Vue, HTML/CSS).

HoangNguyen0403/agent-skills-standard · 47 tokens

system-design-diagramming

Draw system diagrams in the Archify visual language: a typed JSON spec rendered as dark-canvas SVG with numbered lanes, semantic node colors, masked edge labels, and a legend. Covers architecture, workflow, sequence, dataflow, and lifecycle views. Use for any design-session diagram.

HoangNguyen0403/agent-skills-standard · 63 tokens

android-edge-to-edge

Migrate a Jetpack Compose app to edge-to-edge display and fix system bar inset issues. Use when UI components are obscured by navigation/status bars, fixing IME insets, or enabling edge-to-edge for SDK 35+.

HoangNguyen0403/agent-skills-standard · 52 tokens

frontend-design

Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI).…

mastra-ai/mastra · 77 tokens