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/kirti12025/gitlab-mcp/designergit clone --depth 1 https://github.com/kirti12025/gitlab-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/agents/kirti12025/gitlab-mcp/designer)<a href="https://agentmods.dev/agents/kirti12025/gitlab-mcp/designer"><img src="https://agentmods.dev/badge/agents/kirti12025/gitlab-mcp/designer.svg" alt="Measured on agentmods" height="20"></a>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.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 4d 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.
This is a copy
100% identical to designer — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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.
- 4d ago First seen · 80 lines · 39 tokens per session scan A f2994496603f
designer is an agent published in the GitHub repository kirti12025/gitlab-mcp (0 stars, last pushed 1mo ago), 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. It is 100% identical to designer, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
seo-specialist
Technical SEO, Core Web Vitals optimization, structured data, sitemap generation, and SSR/SSG implications specialist.
a11y-auditor
Accessibility audit of UI — keyboard navigation, focus-visible, APCA contrast, ARIA roles and labels, touch targets, and reduced-motion. Use to audit a diff, file, or surface for accessibility issues.
ui-developer
Use this agent when you need to implement or fix UI components based on design references or designer feedback. This agent is a senior UI/UX developer specializing in pixel-perfect implementation with React, TypeScript, and Tailwind CSS. Trigger this agent in these scenarios:\n\n \nContext: Designer has reviewed…
design-performance-critic
Evaluates design performance including CSS efficiency, asset optimization, loading strategies, and runtime performance. Use this agent to ensure generated designs are fast and efficient. Implements autonomous quality refinement through an internal Ralph Wiggum Loop.
html-build
Build agent — generates lecturevN.html from slidedeck.md and designspec.md, integrates images. Use when: designspec.md is locked (Gate 3 approved) and HTML slide file needs to be produced.
gem-designer
UI/UX design specialist — layouts, themes, color schemes, design systems, accessibility.