Borrowing it
Nothing to install: this file belongs to kitariel/expo-mobile-template. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/kitariel/expo-mobile-template/main/.claude/skills/design-system/SKILL.mdgit clone --depth 1 https://github.com/kitariel/expo-mobile-templateWrote 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/kitariel/expo-mobile-template/design-system)<a href="https://agentmods.dev/skills/kitariel/expo-mobile-template/design-system"><img src="https://agentmods.dev/badge/skills/kitariel/expo-mobile-template/design-system/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/kitariel/expo-mobile-template/design-system"><img src="https://agentmods.dev/badge/skills/kitariel/expo-mobile-template/design-system.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.00064 | $0.00398 |
| Opus 5.5 | $0.00026 | $0.00159 |
| Sonnet 5.5 | $0.00013 | $0.00080 |
| Haiku 4.5 | $0.00006 | $0.00040 |
Grade A, and why
design-system 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 2mo 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.
What it actually says
You are applying this Expo template's design system.
Step 1 — read the rules. Read .agents/design-system.md
in the repository root. It is the complete and authoritative specification: the real token
values, the entry-thumbnail pattern, the one active-state rule for tabs and segmented
controls, the empty/loading-state rule, the interaction floors, and the don'ts.
Step 1b — if you are touching a navigation variant, read
.agents/nav-variants.md instead of applying the design
system to it. Rose, Ecommerce, and Void are three deliberately different design languages and
are exempt from the visual rules; only the accessibility floors apply. That file lists each
one's accent, primary-action shape, and badge treatment so they do not cross-pollinate.
Step 2 — read the project context. Read AGENTS.md for the stack,
the conventions, and the current phase.
Step 3 — build. Every value you use comes from a token. If the value you want is not on a ladder, the layout is what needs fixing — not the ladder.
This wrapper deliberately contains no rules of its own, so it can never drift from
.agents/design-system.md. That file is the source of truth, and it is plain markdown so
Codex, Cursor, and Copilot read the same rules from the same place. If the two ever appear to
disagree, .agents/design-system.md wins.
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.
- 2mo ago First seen · 29 lines · 64 tokens per session scan A 4123045ae167
design-system is a skill published in the GitHub repository kitariel/expo-mobile-template (6 stars, last pushed 2mo ago), licensed MIT. It adds 64 tokens to every session and 398 once invoked, about $0.0003 per session on Opus 5.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-08-31.
Other skills, from other repositories
anti-slop-design
Autonomous Principal Design Technologist. Cures vibe-coded software from AI frontend slop using curated token archetypes and 7-axis quality gating.
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.
open-design-setup
Prepare or repair a project's prototyping environment so open-design can build prototypes with the project's own component library and render them through the project's toolchain. Use when the library target is needed and docs/design/prototyping.md is missing, stale, or failing; excludes HTML-only design work and…
frontend-visual-qa
Audits rendered UI and specific task/object-link handoffs; excludes ordinary source citations alone. Audits already-rendered UI and Markdown/Obsidian image layout — web app, deck/slide, dashboard, design-system, or Electron/native app — via real-browser/native-app journeys and a Playwright sweep. Use after UI…