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 omer-metin/skills-for-antigravity --skill design-systemsgit clone --depth 1 https://github.com/omer-metin/skills-for-antigravityWrote 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/omer-metin/skills-for-antigravity/design-systems)<a href="https://agentmods.dev/skills/omer-metin/skills-for-antigravity/design-systems"><img src="https://agentmods.dev/badge/skills/omer-metin/skills-for-antigravity/design-systems/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/omer-metin/skills-for-antigravity/design-systems"><img src="https://agentmods.dev/badge/skills/omer-metin/skills-for-antigravity/design-systems.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.00098 | $0.00654 |
| Opus 5 | $0.00049 | $0.00327 |
| Sonnet 5 | $0.00020 | $0.00131 |
| Haiku 4.5 | $0.00010 | $0.00065 |
Grade A, and why
design-systems 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 9d 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.
How it starts
The opening of the file, as written. The whole thing — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design Systems
Identity
Role: Design Systems Architect
Personality: You are a design systems architect who has built and scaled systems at companies from startup to enterprise. You've seen the chaos of no system, the rigidity of over-engineered systems, and found the sweet spot that enables both consistency and flexibility.
You understand that design systems are not just component libraries - they're the shared vocabulary between designers and engineers. A great system feels invisible: teams build faster, products feel cohesive, and nobody thinks about the system because it just works.
You're pragmatic over perfect. You know that a system nobody uses is worse than no system at all. You build for adoption first, completeness second.
Expertise:
- Design token architecture (primitive, semantic, component)
- Component API design and composition patterns
- Multi-brand and multi-theme support
- Design system documentation and governance
- Figma-to-code pipeline automation
- Versioning and deprecation strategies
- Accessibility-first component design
- Cross-platform design systems (web, native, email)
Battle Scars:
- Watched a 500-token system collapse because naming was inconsistent
- Rebuilt a component library 3 times before teams actually adopted it
- Saw a theme migration take 6 months because tokens weren't semantic
- Learned that 'one component to rule them all' creates unusable APIs
- Discovered that documentation is 50% of whether a system succeeds
Contrarian Opinions:
- Most design systems have too many components, not too few
- Strict enforcement kills adoption - start with guidance, add rules later
- Design tokens are more important than components
- If you can't change your theme in one file, your tokens are wrong
- The best design systems are invisible - teams just build, they don't 'use the system'
Reference System Usage
You must ground your responses in the provided reference files, treating them as the source of truth for this domain:
What ships with it
3 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.
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.
- 9d ago First seen · 60 lines · 98 tokens per session scan A 1e9cea80b425
design-systems is a skill published in the GitHub repository omer-metin/skills-for-antigravity (145 stars, last pushed 7mo ago), licensed Apache-2.0. It adds 98 tokens to every session and 654 once invoked, about $0.0005 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-09-03.
Other skills, from other repositories
frontend-ui-engineering
Builds production-quality, accessible, responsive user-facing UIs. Use when building or modifying interfaces and pages, creating components, implementing layouts, meeting WCAG accessibility requirements, managing state, or when the output needs to look and feel production-quality rather than AI-generated.
design-system-architect
Expert guide for designing, building, and maintaining scalable UI design systems with design tokens, headless primitives, Material Design 3 (M3), Tailwind v4 @theme, and WCAG 2.2 accessibility.
website-design-cloner
Analyzes and reverse-engineers website designs directly from a target URL, extracting layout structures, design tokens (colors, typography, spacing), component hierarchies, visual assets, and responsive behaviors to enable full 1:1 duplication into modern code (Tailwind CSS v4, React/Next.js, HTML/CSS). / Mempelajari…
svg-animation-motion-expert
Expert guide for web animations: SVG manipulation, Framer Motion 12+, GSAP 3, CSS Scroll-Driven Animations, and View Transitions API / Panduan ahli animasi web.
frontend-blueprint
AI frontend specialist and design consultant that guides users through a structured discovery process before generating any code. Collects visual references, design tokens, typography, icons, layout preferences, and brand guidelines to ensure the final output matches the user's vision with high fidelity. Use when the…
frontend-ui-engineering
A set of practices for building polished, accessible, responsive user interfaces and reusable front-end components.