Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/PMDevSolutions/Aureliusnpx agentmods add skills/pmdevsolutions/aurelius/export-design-systemWrote 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/pmdevsolutions/aurelius/export-design-system)<a href="https://agentmods.dev/skills/pmdevsolutions/aurelius/export-design-system"><img src="https://agentmods.dev/badge/skills/pmdevsolutions/aurelius/export-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/pmdevsolutions/aurelius/export-design-system"><img src="https://agentmods.dev/badge/skills/pmdevsolutions/aurelius/export-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.00000 | $0.03129 |
| Opus 5.5 | $0.00000 | $0.01252 |
| Sonnet 5.5 | $0.00000 | $0.00626 |
| Haiku 4.5 | $0.00000 | $0.00313 |
Grade A, and why
export-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 yesterday.
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 — 214 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Export Design System — Publishable Component Library Generator
Purpose
Take generated components and a design-tokens.lock.json and emit a versioned, publishable pnpm workspace:
@scope/design-tokens— framework-agnostic. Ships CSS custom properties, a typed token export, a Tailwind preset, and a JSON snapshot of the lockfile. Anyone (web app, RN app, Storybook, docs site) can consume it.@scope/<framework>-components— framework-specific. Ships compiled components, aThemeProvider+useTheme, and proper peer dependencies. React/Vue/Svelte build with Vite library mode; React Native usestsc(Vite is not part of the RN runtime).
The tokens package is the bridge — every component package depends on it via workspace:^, so updating tokens cascades through every framework target.
When to Use
- After a successful
/build-from-figma,/build-from-canva, or/build-from-screenshotrun, when you want to extract the result as a reusable library rather than ship the full app. - When a design system needs to be published to a private npm registry or installed across multiple consumer apps.
- When migrating from a single-app codebase to a shared component package.
This skill is not part of the autonomous build pipeline — it is invoked on demand via /export-design-system.
Running /export-design-system
$ARGUMENTS holds optional flags for the export script; with none, the framework comes from build-spec.json, the scope from package.json, and the output goes to dist/design-system/.
- Check the preconditions before anything else: a lockfile at
src/styles/design-tokens.lock.jsonordesign-tokens.lock.json, at least one component undersrc/components/(or--components-dir), and a discoverable framework (build-spec.json→outputTarget,package.jsondependencies, or--framework). If one is missing, stop and say which and how to fix it (run a/build-from-*pipeline, pass a flag); never repair the project automatically. - Confirm scope and output once, only when
$ARGUMENTSsets neither: ask for the npm scope (default frompackage.json, else@my-app) and the output directory (defaultdist/design-system) in one question. - Run
./scripts/export-design-system.shwith the resolved flags, forwarding--dry-runand--jsonas given. - Report the framework and scope, the package names (
<scope>/design-tokensand<scope>/<framework>-components), the component count and the output path, then the next steps (cd <output> && pnpm install && pnpm build) and any framework caveat (React Native builds withtsc, not Vite). On a non-zero exit, show the exit code and stderr verbatim and confirm with the user before trying a remedy.
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.
- yesterday Changed · +14 lines cad7235bed01
- 1mo ago First seen · 200 lines · 0 tokens per session scan A 4fb152714040
export-design-system is a skill published in the GitHub repository PMDevSolutions/Aurelius (9 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,129 tokens. 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-04.
Other skills, from other repositories
mk:figma
Read-first Figma gateway via Figma MCP: analyze designs, implement Figma-to-code for 1–3 screens, extract design tokens, produce a Figma Evidence Packet for planning handoff, screenshot fallback. Advanced operations (Code Connect, canvas writes, design-system/library patterns) are gated references loaded only on…
generate-project-design-system
A draft generator that studies a project's code and Figma design data to prepare a design-system skill. A design system is a shared set of colors, sizes, components, and usage rules for keeping interfaces consistent.
figma-codegen
Generate framework-aware code from a Figma design. Reads the project's stack profile and emits code matching the existing framework (React/Vue/Svelte/Next/etc.) and styling (Tailwind/CSS/CSS-in-JS), reusing existing components and design tokens instead of regenerating from scratch. Triggers whenever the user wants a…
figma-build
Build a Figma design from code or a description — the reverse of figma-codegen. Reuses the connected file's existing design system (components, variables, styles) instead of drawing primitives with hardcoded values. Triggers whenever the user wants something created or updated IN Figma from code or a spec — e.g.…
refero-design
Primary/default skill for UI design, product design, web design, landing pages, dashboards, product screens, redesigns, visual polish, frontend/CSS styling, design systems, components, responsive design, typography, color, spacing, motion, icons, accessibility, copywriting, conversion, and anti-AI-slop work. Use this…
producao-no-figma
Orientação para organização e produção em Figma: componentes, auto-layout e sistemas de design.