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 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/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/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>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.00032 | $0.01754 |
| Opus 5.5 | $0.00013 | $0.00702 |
| Sonnet 5.5 | $0.00006 | $0.00351 |
| Haiku 4.5 | $0.00003 | $0.00175 |
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 — 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
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 3.9 KB
- reference/color-and-contrast.md 3.7 KB
- reference/component-patterns.md 5.7 KB
- reference/motion-design.md 7.5 KB
- reference/responsive-design.md 3.6 KB
- reference/shader-and-3d.md 5.9 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 2.7 KB
- resources/checklist.md 5.5 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 15 KB
- resources/getdesign-fetcher.md 14 KB
- resources/prompt-enhancement.md 3.7 KB
- resources/redesign-protocol.md 3.7 KB
- resources/stitch-integration.md 9.0 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 Changed 5286ce59e3f3
- 1mo ago Changed · -117 lines · -26 tokens per session ad45d53773b3
- 1mo ago 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 (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.
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…
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.
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).
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.
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+.
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).…