A command for removing a design-system library and its stored cache and state. A design-system library contains shared interface styles and components used by a project.

Use it to remove a named library, or to list available libraries and choose one.

It clears out an old or incorrectly added library and shows what will be removed before deletion.

ds-remove — Command by atezer

Install

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.

agentmods

npx agentmods add commands/atezer/fmcp/ds-remove

Clone the repo

git clone --depth 1 https://github.com/atezer/FMCP

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,323 The whole file, excluding the scripts and references it only reads on demand.

Security scan C 1 finding. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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	$0.00000	$0.01323
Opus 5	$0.00000	$0.00661
Sonnet 5	$0.00000	$0.00265
Haiku 4.5	$0.00000	$0.00132

Measured 2d ago against content hash d795efe75f37, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade C, and why

ds-remove scanned grade C with 1 finding 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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

rm -rf .claude/design-systems/<id>/

commands/ds-remove.md · 126 lines

How it starts

The opening of the file, as written. The whole thing — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Tasarım Sistemi Kütüphanesini Kaldır

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.

Argüman

$ARGUMENTS

Argüman olabilir:

<library-id> → o kütüphaneyi kaldır
Boş → kullanıcıya hangi DS'in kaldırılacağını sor

Adım 1: Hedef Belirleme

$ARGUMENTS boşsa:
- .claude/design-systems/ altındaki kütüphaneleri listele (README.md, active-ds.md, last-intent.md, intent-history.md haricindeki alt-dizinler)
- Kullanıcıya sor: "Hangi kütüphaneyi kaldırayım? Mevcut DS'ler: [liste]. Yazın veya 'iptal' deyin."

Kütüphane ID → .claude/design-systems/<id>/ dizini yoksa:

❌ "<id>" adında bir kütüphane bulunamadı.
💡 Mevcut kütüphaneleri görmek için: ls .claude/design-systems/

Adım 2: Etki Özeti (Silmeden Önce Göster)

Kaldırılacak şeyleri topla ve kullanıcıya göster:

⚠️ "<library-id>" kütüphanesi kaldırılacak. Etki:

📁 Silinecek repo dizinleri:
- .claude/design-systems/<id>/ (<N> dosya: tokens.md, components.md, ...)

🗑️  Silinecek user-local cache (gerçek key'ler):
- ~/.claude/data/fcm-ds/<file-key-1>/
- ~/.claude/data/fcm-ds/<file-key-2>/ (varsa secondary libraries)

📝 Güncellenecek state dosyaları:
- .claude/design-systems/active-ds.md (Primary Library <id> → ❌ Henüz seçilmedi)
- ~/.claude/data/fcm-ds/active.md (Library Map'ten <id> kaldırılacak)
- .claude/design-systems/last-intent.md (eğer <id> son intent ise → sıfırla)

⚠️ Bu işlem GERİ ALINAMAZ. Devam edeyim mi? (evet / iptal)

User "iptal" derse → DUR. User "evet" derse → Adım 3'e geç.

Adım 3: User-Local Cache Key'lerini Çıkar

~/.claude/data/fcm-ds/active.md dosyasını oku; silinecek DS'in primary + secondary file-key'lerini topla.

Eğer user-local active.md eski format (tek File Key: satırı) ise → o tek key'i kullan. Yeni format (Library Map tablosu) ise → tüm satırlardaki key'leri topla.

Read the full file on GitHub · 126 lines

Changes

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 · 126 lines · 0 tokens per session scan C d795efe75f37

Subscribe to this mod's changes

ds-remove is a command published in the GitHub repository atezer/FMCP (9 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,323 tokens. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Frontend ai claude cursor design-system design-tokens figma

ds-remove

Getting it into your agent

What it costs to keep this loaded

Grade C, and why

Recursive force deletehighDestructive command

How it starts

Tasarım Sistemi Kütüphanesini Kaldır

Argüman

Adım 1: Hedef Belirleme

Adım 2: Etki Özeti (Silmeden Önce Göster)

Adım 3: User-Local Cache Key'lerini Çıkar

What this file has done since we first saw it

Other commands, from other repositories

full-diagnostic

describe-component

docs-coverage

governance-review

release-check

component-audit