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/jmstar85/oh-my-githubcopilot/designergit clone --depth 1 https://github.com/jmstar85/oh-my-githubcopilotWhat 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.00705 |
| Opus 5 | $0.00019 | $0.00352 |
| Sonnet 5 | $0.00008 | $0.00141 |
| Haiku 4.5 | $0.00004 | $0.00071 |
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.
This is a copy
89% identical to designer — 4 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.
- 2d ago First seen · 80 lines · 39 tokens per session scan A e1606fbef907
designer is an agent published in the GitHub repository jmstar85/oh-my-githubcopilot (153 stars, last pushed 3mo ago), licensed MIT. It adds 39 tokens to every session and 705 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 89% identical to designer, differing in 4 lines, and is treated as a copy.
Other agents, from other repositories
cli-ui-designer
CLI interface design specialist. Use PROACTIVELY to create terminal-inspired user interfaces with modern web technologies. Expert in CLI aesthetics, terminal themes, and command-line UX patterns.
building-blocks
SVG-based building block components and shared utilities.
core-frontend
Frontend implementation specialist. Use when the task involves UI components, pages, layouts, styling, animations, client-side logic, or anything the user sees and interacts with. Focuses on UX quality, accessibility, and cross-device reliability.
frontend-styling-agent
Agent "frontend-styling-agent" from girijashankarj/cursor-handbook, covering styling agent, invocation, scope, expertise and when to use.
fec-ui-checker
Use this subagent to troubleshoot visual defects, layout confusion, CSS issues, responsive exceptions, and inconsistencies between interaction and design in the front-end UI, and save the report as a Markdown file. Supports obtaining design data from Figma, Sketch, MasterGo, Pixso, Moko, and Mock, compares the design…
superpowers-sage:visual-verifier
Compares implemented sections against design reference using screenshots; reads plan spec files and reference images, captures implementation via Playwright MCP, checks for arbitrary Tailwind values, reports visual match, drift, or missing elements.