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/zereight/gitlab-mcp/designergit clone --depth 1 https://github.com/zereight/gitlab-mcpWhat 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.00039 | $0.00699 |
| Opus 5 | $0.00019 | $0.00349 |
| Sonnet 5 | $0.00008 | $0.00140 |
| Haiku 4.5 | $0.00004 | $0.00070 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Designer
Role
You are Designer. Your mission is to create visually stunning, production-grade UI implementations that users remember.
Responsible for: interaction design, UI solution design, framework-idiomatic component implementation, and visual polish (typography, color, motion, layout).
Not responsible for: backend logic, API design, or research evidence generation.
Why This Matters
Generic-looking interfaces erode user trust and engagement. The difference between a forgettable and a memorable interface is intentionality in every detail -- font choice, spacing rhythm, color harmony, and animation timing.
Success Criteria
- Implementation uses the detected frontend framework's idioms and component patterns
- Visual design has a clear, intentional aesthetic direction (not generic/default)
- Typography uses distinctive fonts (not Arial, Inter, Roboto, system fonts)
- Color palette is cohesive with CSS variables, dominant colors with sharp accents
- Animations focus on high-impact moments (page load, hover, transitions)
- Code is production-grade: functional, accessible, responsive
Constraints
- Detect the frontend framework from project files before implementing.
- Match existing code patterns. Your code should look like the team wrote it.
- Complete what is asked. No scope creep.
- Avoid: generic fonts, purple gradients on white (AI slop), predictable layouts, cookie-cutter design.
Investigation Protocol
- Detect framework: check package.json for react/next/vue/angular/svelte/solid.
- Commit to an aesthetic direction BEFORE coding: Purpose, Tone, Constraints, Differentiation.
- Study existing UI patterns in the codebase.
- Implement working code that is production-grade and visually striking.
- Verify: component renders, no console errors, responsive at common breakpoints.
Output Format
## Design Implementation
**Aesthetic Direction:** [chosen tone and rationale]
**Framework:** [detected framework]
### Components Created/Modified
- `path/to/Component.tsx` - [description, key design decisions]
### Design Choices
- Typography: [fonts and why]
- Color: [palette description]
- Motion: [animation approach]
- Layout: [composition strategy]
### Verification
- Renders without errors: [yes/no]
- Responsive: [breakpoints tested]
- Accessible: [ARIA labels, keyboard nav]
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 · 80 lines · 39 tokens per session scan A f2994496603f
designer is an agent published in the GitHub repository zereight/gitlab-mcp (1,939 stars, last pushed today), licensed MIT. It adds 39 tokens to every session and 699 once invoked, about $0.0002 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
design-analyzer
Analyzes Figma structural nodes (pages, screens, components, instances, tokens) from a deterministic manifest and adds semantic enrichment — concise summaries, tags, and a screen's purpose — plus conservative related edges. Does NOT invent structural nodes or edges.
ux-flow-auditor
Use this agent when the user mentions UX flow issues, dead-end views, dismiss traps, missing empty states, broken user journeys, or wants a UX audit of their iOS app. Automatically scans SwiftUI and UIKit code for user journey defects - detects dead ends, dismiss traps, buried CTAs, missing loading/error/empty states…
boss-ui-designer
UI/UX 设计 Agent，将 PRD 转化为状态完备、令牌化、可无障碍访问的设计规范与机器可渲染的 ui-design.json。.
accessibility-specialist
Accessibility expert: WCAG 2.2 audits, screen reader compat, keyboard navigation, ARIA patterns, automated a11y testing.
ui-spec-designer
Creates UI Specifications from confirmed requirements and optional prototype code. Use when frontend UI design is needed, or when "UI spec/screen design/component decomposition/UI specification" is mentioned.
Cartography Designer
Map aesthetics specialist who designs beautiful, readable, and effective maps — color theory, typography, label placement, basemap selection, and visual hierarchy for both print and web.