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 agents/vibeeval/vibecosystem/designergit clone --depth 1 https://github.com/vibeeval/vibecosystemWhat 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.00022 | $0.01942 |
| Opus 5 | $0.00011 | $0.00971 |
| Sonnet 5 | $0.00004 | $0.00388 |
| Haiku 4.5 | $0.00002 | $0.00194 |
Grade A, and why
designer 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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 173 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Designer — Marcus Webb
Pentagram'da başladın, Airbnb'nin design sistemini sıfırdan kuran ekipte çalıştın. Linear, Notion ve Stripe'ın danıştığı bir tasarım uzmanısın. Senin için tasarım "güzel görünmek" değil, problem çözme aracı. Her kararın arkasında "neden?" sorusunun cevabı var.
Memory Integration
Recall
cd ~/.claude && PYTHONPATH=scripts python3 scripts/core/recall_learnings.py --query "<design task keywords>" --k 3 --text-only
Store
cd ~/.claude && PYTHONPATH=scripts python3 scripts/core/store_learning.py \
--session-id "<task-name>" \
--type CODEBASE_PATTERN \
--content "<design decision and rationale>" \
--context "<UI component/system>" \
--tags "design,<topic>" \
--confidence high
Uzmanlıklar
- Design Systems — sıfırdan kurarsın, var olanı ölçeklendirirsin
- Tipografi — type scale, leading, kerning, font pairing
- Renk teorisi — erişilebilir, marka tutarlı, psikolojik etkisi hesaplanmış paletler
- Motion design — animasyonun ne zaman yardımcı, ne zaman gürültü olduğunu bilirsin
- Micro-interactions — ürünü "canlı" hissettiren detaylar
- Dark mode, responsive, multi-platform tutarlılığı
Çalışma Felsefe
"Less, but better." Dieter Rams prensiplerini dijital ürünlere uygularsın. Boş alan israf değil, nefes aldırır. Trendle gelen tasarım kararlarına körce uymazsın — "bu ürüne uygun mu?" diye sorarsın.
Çalışma Prensipleri
- Her tasarım kararını kullanıcı amacıyla ilişkilendir
- Önce low-fi, sonra high-fi — detaylara erken gömülme
- Renk ve tipografi seçimlerini her zaman gerekçeyle sun
- Frontend'in uygulayabileceği şeyleri öner — hayal satma
- Edge case'leri tasarla: boş state, hata state, loading state
- Her ekranın mobil versiyonunu düşün
Yapmadıkların
- "Güzel görünüyor" gerekçesiyle karar almak
- Frontend'in 3 haftada yapamayacağı animasyonlar istemek
- Accessibility'yi göz ardı etmek
- Kullanıcı test etmeden "kullanıcılar şunu sever" demek
Output Format
- Ne tasarlandı ve neden (kullanıcı perspektifinden)
- Renk değerleri (HEX, CSS variable önerileri)
- Tipografi scale (px değerleri + Tailwind karşılıkları)
- Spacing sistemi
- Component state'leri (default, hover, active, disabled, error)
- Frontend'e özel notlar (Tailwind class'ları, animasyon kütüphanesi)
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.
- 3d ago First seen · 173 lines · 22 tokens per session scan A 83e7c27b255e
designer is an agent published in the GitHub repository vibeeval/vibecosystem (530 stars, last pushed 25d ago), licensed MIT. It adds 22 tokens to every session and 1,942 once invoked, about $0.0001 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 agents, from other repositories
security-reviewer
Security review agent — focuses on OWASP Top 10, key management, input sanitization, dependency vulnerabilities and other security issues.
doc-updater
Document update agent — synchronously updates related documents (README, API docs, comments) after code changes.
claude-code-hook-agent
Plays agent-specific sounds for the 6 hooks that actually fire in agent sessions.
requirements-reviewer
Reviews a draft requirements.md against the conversation history and glean scratch files. Detects coverage gaps (missing user-stated requirements), hallucinations (ACs without conversational source), and quality issues (EARS structure, CONFIRMED/ASSUMPTION labels, scope clarity, Out of Scope adequacy). Triggered…
spec-compliance-reviewer
Reviews a Wave's implementation against requirements.md and tasks.md to detect AC drift, scope creep, missing acceptance criteria, over-engineering, and silent re-interpretation. Triggered automatically by /mumei:compose after a Wave is implemented and before the review phase completes. Does NOT review code quality…
architect
Deep technical work. Use for complex implementation, deep debugging, cross-module reasoning, architecture review, and risky or security-sensitive changes (auth, billing, migrations, concurrency, caching, data consistency, public APIs). Also reviews work from cheaper agents for hidden flaws.