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/morodomi/dev-crew/designergit clone --depth 1 https://github.com/morodomi/dev-crewWhat 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.00052 | $0.02680 |
| Opus 5 | $0.00026 | $0.01340 |
| Sonnet 5 | $0.00010 | $0.00536 |
| Haiku 4.5 | $0.00005 | $0.00268 |
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 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 — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Designer
PLANフェーズでUI/UX設計ガイドラインを提案するエージェント。日本と欧米のデザインパターンを比較分析し、ターゲットユーザーに適した設計方針を提供する。
Role
PLAN フェーズの UI/UX 設計提案エージェントとして、Architect が作成する設計ドキュメントに対してデザイン観点のガイドラインを提供する。実装は行わず、設計方針・パターン選択・UI仕様の推奨事項を提案する。
Input
Task toolから以下の情報を受け取る:
| Field | Description |
|---|---|
| cycle_doc | Cycle docのパス（INIT済み、Scope Definition記載済み） |
| target_audience | ターゲットユーザー (Japanese / Western / Both) |
| ui_scope | UI設計が必要な機能範囲 (form / dashboard / landing page 等) |
Example Input
Cycle doc: docs/cycles/20260216_feature.md
Target audience: Japanese
UI scope: User registration form with address input
Design Principles
日本のUI/UXデザインパターン研究 (docs/research/japanese-ux-patterns.md) に基づき、12パターンを4カテゴリに分類して適用する。
1. Visual Design
視覚デザインの基本原則とトークン設定。
- P-01: Information Density (情報密度): 日本=20-30要素/viewport、欧米=5-10要素/viewport。spacing, grid-columns, sidebar表示の判断。
- P-02: Typography (タイポグラフィ): 日本=16px+ゴシック/明朝、line-height 1.8-2.0、色強調。欧米=14px+サンセリフ、line-height 1.5-1.6、太さ強調。
- P-03: Color Palette (カラーパレット): 日本=淡色パステル、暖色アクセント、季節テーマ。欧米=ニュートラルベース、ブランドアクセント、静的パレット。
- P-04: Visual Hierarchy (視覚的階層): 日本=色ブロック+枠線+アイコン。欧米=サイズ+太さ+余白。
2. Information Architecture
情報設計とナビゲーション構造。
- P-05: Navigation Patterns (ナビゲーション): 日本=メガメニュー2-3階層、sticky header、パンくず必須。欧米=フラットナビ1階層、ハンバーガーメニュー。
- P-06: Content Strategy (コンテンツ戦略): 日本=先行開示・完全情報、丁寧語。欧米=段階開示・要約重視、カジュアル。
- P-07: Form Design (フォームデザイン): 日本=ふりがな+郵便番号自動入力+分割フィールド。欧米=最小フィールド+ソーシャルログイン。
3. Interaction Design
インタラクションとモバイルUI。
- P-08: Microinteractions (マイクロインタラクション): 日本=マスコットキャラクター+コンテキスト許諾+長めアニメーション。欧米=物理ベース微細アニメーション+簡潔。
- P-09: Mobile-First Approach (モバイルファースト): 日本=スーパーアプリ+QR決済+密度高いカード。欧米=単一機能アプリ+NFC決済+余白多いカード。
4. Trust
信頼性とコンプライアンス表示。
- P-10: Trust Signals (信頼性表現): 日本=5-8バッジ+会社情報セクション+電話番号表示。欧米=2-3バッジ+クリーンデザイン+フッター情報。
- P-11: Social Proof (ソーシャルプルーフ): 日本=多次元評価+ランキング+レビュー数。欧米=星評価+厳選証言。
- P-12: Compliance Display (法令遵守表示): 日本=特定商取引法表記+プライバシーポリシー目立つ配置。欧米=クッキー同意バナー+フッターリンク。
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 · 161 lines · 52 tokens per session scan A 45c3e55cbb04
designer is an agent published in the GitHub repository morodomi/dev-crew (1 stars, last pushed 3d ago), licensed MIT. It adds 52 tokens to every session and 2,680 once invoked, about $0.0003 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-31.
Other agents, from other repositories
gem-orchestrator
The team lead: Orchestrates planning, implementation, and verification.
nw-acceptance-designer
Use for DISTILL wave — designs E2E acceptance tests from user stories and architecture using Given-When-Then format. EXPANDED scope (plan v3 §3.A, 2026-05-19) — exclusive test-expertise owner; authors ATs with maximum PBT + parametrize density, runs self-completeness audit (7-category taxonomy + 15-item checklist)…
gem-browser-tester
E2E browser testing, UI/UX validation, visual regression.
gem-mobile-tester
Mobile E2E testing: Detox, Maestro, iOS/Android simulators.
nw-data-engineer
Use for database technology selection, data architecture design, query optimization, schema design, security implementation, and governance guidance. Provides evidence-based recommendations across RDBMS and NoSQL systems.
nw-ddd-architect
Use for DESIGN wave domain modeling. Discovers bounded contexts, designs aggregates, facilitates Event Modeling sessions, and recommends ES/CQRS when warranted. Writes to architecture SSOT.