Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
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.
[](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.svg" alt="Measured on agentmods" 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.00102 | $0.02669 |
| Opus 5 | $0.00051 | $0.01334 |
| Sonnet 5 | $0.00020 | $0.00534 |
| Haiku 4.5 | $0.00010 | $0.00267 |
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 — 200 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.
Inputs
- Required:
design-tokens.lock.json(auto-detected atsrc/styles/design-tokens.lock.jsonordesign-tokens.lock.json)- At least one component file under
src/components/(or override with--components-dir)
- Optional:
build-spec.json(auto-detected at.claude/plans/build-spec.jsonorbuild-spec.json) — read foroutputTarget. If absent, framework is inferred frompackage.jsondeps or supplied via--framework.--scope <name>— npm scope. Defaults to the existingpackage.jsonscope, or@my-app.--output <dir>— where to write the workspace. Default:dist/design-system/.
Outputs
A complete pnpm workspace at <output>/:
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 First seen · 200 lines · 0 tokens per session scan A 4fb152714040
export-design-system is a skill published in the GitHub repository PMDevSolutions/Aurelius (8 stars, last pushed 21d ago), licensed MIT. It adds 102 tokens to every session and 2,669 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-04.
Other skills, from other repositories
figma-design-handoff
Figma-to-code design handoff patterns including Figma Variables to design tokens pipeline, component spec extraction, Dev Mode inspection, Auto Layout to CSS Flexbox/Grid mapping, and visual regression with Applitools. Use when converting Figma designs to code, documenting component specs, setting up design-dev…
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
현재 프로젝트의 디자인 시스템을 분석하여 project-design-system 스킬의 초안을 생성합니다. Figma MCP의 createdesignsystemrules와 getvariabledefs를 활용하고, 코드베이스를 분석하여 Figma 토큰 → 코드 매핑 규칙을 도출합니다. 초안 생성 후 /skill-creator와 사용자 피드백으로 다듬는 과정이 필요합니다. "디자인 시스템 스킬 만들어줘", "project-design-system 생성" 같은 요청에 사용하세요.
mcp-sdk-audit
Upgrade @modelcontextprotocol/server (the MCP TypeScript SDK v2) and prove the wire contract survived. The SDK is a runtime dependency whose breakage lands on the wire, not in the type checker — so this sorts each release by which SDK source files it touched (Figwright uses only the server + stdio slice of a…
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.…