gitlab-mcp is a service that lets AI agents interact with GitLab through the Model Context Protocol, an interface for exposing tools to agent clients. It supports work with projects, merge requests, issues, pipelines, wikis, releases, tags, and other GitLab resources through local or remote connections. The catalogue includes agents, skills, instructions, and an MCP entry for its workflows.
Borrowing it
Nothing to install: this file belongs to zereight/gitlab-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/zereight/gitlab-mcp/main/.github/agents/designer.agent.mdgit clone --depth 1 https://github.com/zereight/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/zereight/gitlab-mcp/designer)<a href="https://agentmods.dev/agents/zereight/gitlab-mcp/designer"><img src="https://agentmods.dev/badge/agents/zereight/gitlab-mcp/designer/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/zereight/gitlab-mcp/designer"><img src="https://agentmods.dev/badge/agents/zereight/gitlab-mcp/designer.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00039 | $0.00699 |
| Opus 5.5 | $0.00016 | $0.00280 |
| Sonnet 5.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 1mo 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.
- 1mo ago First seen · 80 lines · 39 tokens per session scan A f2994496603f
designer is an agent published in the GitHub repository zereight/gitlab-mcp (2,047 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.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
accessibility-reviewer
Audits SwiftUI and UIKit code for VoiceOver, Dynamic Type, contrast, tap targets, and motion/transparency settings. Read-only — reports findings with file:line and the specific fix. Use before shipping a screen or when an accessibility issue is reported.
designer
Design routing and UI/UX specialist — owns contextual selection among design skills (frontend-design, frontend-design-review, web-design-guidelines, design-assessment, design-improvement, scroll-world, Figma family, brag/brag-slim, accessibility/review). Use when: new visual direction, design review, WIG audit…
frontend-ui-component-agent
/ui-component-agent or @ui-component-agent.
metago-presentation-designer
Presentation Designer - specializes in PPT outlines, slide layouts, whitepaper layouts, and template recommendations.
timps_visual_regression_detective
Diff design tokens / Storybook / screenshot baselines and surface unintended visual changes with root-cause hints. Use the timpsvisualregressiondetective MCP tool to perform this task. Do not answer directly — delegate to this sub-agent.
accessibility-reviewer
Use this agent to judge WCAG 2.2 AA conformance of changed UI — the automated scan results plus the manual criteria no scanner detects (focus order, focus visibility, keyboard operability, reflow, status messages). Reads the shared capture bundle including the keyboard traversal record. See "When to invoke" in the…