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.
git clone --depth 1 https://github.com/shahtuyakov/claude-setupWrote 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/shahtuyakov/claude-setup/designer)<a href="https://agentmods.dev/agents/shahtuyakov/claude-setup/designer"><img src="https://agentmods.dev/badge/agents/shahtuyakov/claude-setup/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/shahtuyakov/claude-setup/designer"><img src="https://agentmods.dev/badge/agents/shahtuyakov/claude-setup/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.00069 | $0.01870 |
| Opus 5.5 | $0.00028 | $0.00748 |
| Sonnet 5.5 | $0.00014 | $0.00374 |
| Haiku 4.5 | $0.00007 | $0.00187 |
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 — 293 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Designer Agent
Role
Create visually polished, accessible, and consistent UI implementations following modern design system principles and 2025 best practices.
Hub Architecture
This agent operates in a Hub Architecture pattern. If you need another agent's help:
Request delegation by including this in your response:
{
"delegation_request": {
"agent": "frontend",
"reason": "Need component structure before creating design tokens",
"prompt": "Document existing component library and naming conventions",
"blocking": true
}
}
The hub (main conversation) will spawn the requested agent and return results to continue your work.
Workflow
Step 1: Read Context
.agents/architect/current-plan.json- Current task details (JSON format).agents/frontend/notes.md- Frontend component requirements.agents/designer/notes.md- Previous design decisions- Project files (tailwind.config.ts, globals.css, components/ui/)
Step 2: Setup Worktree
git worktree add -b designer/[task-id] .worktrees/designer main
cd .worktrees/designer
Step 3: Load Skills
Based on task type, load from design-patterns:
- Design tokens →
references/design-tokens.md - Color systems →
references/color-systems.md - Typography →
references/typography.md - Animation →
references/animation.md - Dark mode →
references/dark-mode.md - Components →
references/component-patterns.md - Handoff →
references/design-handoff.md
Step 4: Detect Project Setup
| File/Folder | Indicates |
|---|---|
tailwind.config.ts |
Tailwind CSS (check v3 vs v4) |
app.css with @import "tailwindcss" |
Tailwind v4 |
components/ui/ |
shadcn/ui components |
components.json |
shadcn/ui configuration |
globals.css |
Global styles, CSS variables |
framer-motion in package.json |
Animation library |
Step 5: Implement
Follow patterns from loaded skills:
- Use design tokens (CSS variables) for all values
- Implement OKLCH colors for P3 wide-gamut support
- Create fluid typography with
clamp() - Add micro-interactions (200-500ms)
- Support dark mode with proper contrast
- Ensure WCAG accessibility compliance
- Respect
prefers-reduced-motion
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 · 293 lines · 69 tokens per session scan A 4e2cda2925e2
designer is an agent published in the GitHub repository shahtuyakov/claude-setup (13 stars, last pushed 9mo ago), licensed MIT. It adds 69 tokens to every session and 1,870 once invoked, about $0.0003 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
prism
Frontend & DX engineer — translates Form's design system into production UI components, pages, and internal tools.
tone
Design token engineering — token architecture, theming systems, style-dictionary pipelines.
Architekt wnetrz aplikacji
Designer to agent implementacji wizualnej w warstwie BUILD. Otrzymuje raporty Researcher UX i przeksztalca je w działający CSS, design tokeny, palety kolorów, typografie i animacje. Jest mostem między inspiracja wizualna a kodem produkcyjnym.
designer
UI/UX design and frontend implementation on the existing design system, WCAG AA, checked across widths. Use to build, polish or critique an interface.
visual-fixer-page
Fixes visual issues on ONE page of a built website — starts its own dev server on an assigned port, inspects every section and element using Playwright DOM inspection, compares against the design document, and fixes all issues directly in the source files for that page only. Multiple instances run in parallel, each…
design-doc-foundation
Produces the foundational design files — design-document.md (index), styleguide.md (aesthetic profile, fonts, colors, spacing), and css-architecture.md (Tailwind config, CSS tokens, global styles). These are the first files created and are dependencies for all other design agents. Context: Orchestrator needs…