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/commands/pmdevsolutions/aurelius/export-design-system)<a href="https://agentmods.dev/commands/pmdevsolutions/aurelius/export-design-system"><img src="https://agentmods.dev/badge/commands/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.00000 | $0.01084 |
| Opus 5 | $0.00000 | $0.00542 |
| Sonnet 5 | $0.00000 | $0.00217 |
| Haiku 4.5 | $0.00000 | $0.00108 |
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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/export-design-system — Export Components as a Publishable Library
Export the generated components and design tokens from this project as a publishable pnpm workspace with a framework-agnostic token package and a framework-specific component library (Vite library mode for web, tsc for React Native).
Input
$ARGUMENTS — optional flags forwarded to the export script. Common patterns:
- (none) — default: detect framework from
build-spec.json, scope frompackage.json, output todist/design-system/. --scope @acme— override the npm scope.--output packages/design-system— pick a different output location.--framework vue— override detected framework.--dry-run— preview without writing.--force— overwrite existing output dir.--json— machine-readable summary.
Preconditions
This command requires:
design-tokens.lock.jsoninsrc/styles/or project root (produced by thedesign-token-lockskill or any of the/build-from-*pipelines).- At least one component in
src/components/(or pass--components-dir). - Framework discoverable via
build-spec.json(outputTarget),package.jsondeps, or--frameworkflag.
If any precondition is missing, stop and tell the user which one and how to fix it (run a build pipeline, pass a flag, etc.) — do not attempt to repair the project automatically.
Steps
1. Sanity check inputs
Run a quick detection pass before invoking the skill:
test -f src/styles/design-tokens.lock.json || test -f design-tokens.lock.json
ls src/components 2>/dev/null | head -1
If lockfile is missing, surface the error and recommend running /build-from-figma, /build-from-canva, or /build-from-screenshot first.
2. Confirm scope and output (only if user did not pass them)
If the user did not provide --scope or --output, ask them once via AskUserQuestion:
- Scope: "What npm scope should the packages publish under? (e.g.
@acme)" — default to the value detected from the project'spackage.json, or@my-app. - Output dir: offer
dist/design-systemas the default and let them confirm or override.
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 · 111 lines · 0 tokens per session scan A 29b55f7644df
export-design-system is a command published in the GitHub repository PMDevSolutions/Aurelius (8 stars, last pushed 21d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,084 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 commands, from other repositories
dashboard-layout
Design and build a complete dashboard layout — sidebar navigation, KPI cards, chart areas, data tables, filter bar, and responsive behavior. Outputs production-ready HTML/CSS.
figma-start
디자이너가 개발자의 원본 PR 위에서 검수를 시작할 때 호출하는 커맨드입니다. PR 링크 하나만 주면 프로젝트 클론부터 합니다 — 검수할 프로젝트를 미리 받아둘 필요가 없습니다. 브랜치 생성·체크아웃 후 빌드해서 기기에 올려 화면까지 띄워줍니다 — 실행할 기기·에뮬레이터가 없으면 검수에 맞는 걸 설치해서 만듭니다. 그 브랜치의 커밋 이력 패널도 개발툴에 띄워줍니다 — 지금까지 반영한 검수 내용을 검수 내내 옆에 두고 볼 수 있습니다. 커밋·푸시는 하지 않습니다. 디자이너가 화면을 먼저 확인한 뒤, 필요하면 /figma-apply로 피그마 변경을 반영합니다.
handoff
디자이너 작업 완료 신호 — design/ 브랜치로 dev 브랜치 타겟 PR을 만들고, 원본 dev PR 작성자를 리뷰어로 지정.
figma-apply
피그마 변경을 현재 design/ 브랜치에 반영(커밋·푸시). /figma-start 이후에 사용.
sheleg-design
Apply the SHELEG Design methodology (single-clock, layered, degrade-to-calm motion) to the current landing-page / hero / scroll-animation task — or its style packs to product UI (dashboards, admin, internal tools).
revisar-ui
Auditoria visual retroativa de 6 pilares do código frontend implementado.