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 agentmods add commands/murphytrueman/design-system-ops/migrationgit clone --depth 1 https://github.com/murphytrueman/design-system-opsWhat 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 | $0.00007 | $0.00150 |
| Opus 5 | $0.00003 | $0.00075 |
| Sonnet 5 | $0.00001 | $0.00030 |
| Haiku 4.5 | $0.00001 | $0.00015 |
Grade A, and why
migration 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 2d 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
Run the migration agent to plan and execute a design system migration.
Load the migration agent from ${CLAUDE_PLUGIN_ROOT}/skills/migration-agent.md and follow its complete workflow.
The user should describe the migration context: $ARGUMENTS
The agent chains multiple skills (token-audit, codemod-generator, deprecation-process, change-communication) into a coordinated migration plan with impact analysis, codemods, communication packages, and rollback strategy.
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.
- 2d ago First seen · 13 lines · 7 tokens per session scan A 3fbb6add311b
migration is a command published in the GitHub repository murphytrueman/design-system-ops (174 stars, last pushed 11d ago), licensed MIT. It adds 7 tokens to every session and 150 once invoked, about $0.0000 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-08-30.
Other commands, from other repositories
ds-add
Kullanıcı bir Figma linki ile yeni tasarım sistemi eklemek istediğinde bu komutu kullan. Bu komut yeni ekleme ve güncelleme arasındaki farkı otomatik tespit eder.
ds-sync
Mevcut bir tasarım sistemi kütüphanesini Figma'dan senkronize eder. Tam sync, kısmi sync ve resume (yarım kalanı devam ettirme) destekler.
add-library
Kullanıcı "kütüphane ekle", "library ekle", "tasarım sistemi ekle", "design system ekle" dediğinde bu komutu uygula.
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).
ds-remove
Kullanıcı "kütüphane kaldır", "library sil", "DS'i kaldır", "DS'i sil", "tasarım sistemini kaldır" dediğinde bu komutu uygula. Kullanıcı eski/yanlış eklenmiş bir DS'in cache'ini ve state'ini temizlemek ister.
pack
Bundle every designlang output (DTCG tokens, Tailwind, shadcn, Figma vars, motion, anatomy, Storybook, prompts) into one polished design-system directory ready to zip and ship.