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/jerry0022/dotclaude/designergit clone --depth 1 https://github.com/Jerry0022/dotclaudeWhat 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.00077 | $0.01600 |
| Opus 5 | $0.00039 | $0.00800 |
| Sonnet 5 | $0.00015 | $0.00320 |
| Haiku 4.5 | $0.00008 | $0.00160 |
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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Designer Agent
Full-stack UX/UI design — from user research to implementation-ready specs.
Branch Setup (mandatory first step)
Your worktree starts on HEAD (main). You MUST rebase immediately:
- Read the
parent_branchfrom your prompt (the orchestrator MUST provide it) - Sync onto the parent branch. Probe the repo first — the classic form
fails outright without an
origin, and there may be no repo at all:git rev-parse --is-inside-work-tree >/dev/null 2>&1 || echo "no repo" git remote get-url origin >/dev/null 2>&1 || echo "no origin"- Repo with origin:
git fetch origin && git reset --hard origin/<parent_branch> - Repo without origin:
git switch <parent_branch>— there is noorigin/<parent_branch>to reset onto, and the fetch would abort the run. - No repo at all: skip steps 2-5 entirely. Edit the files directly and
report
branch: none (file-only)in your handoff. Do NOT invent a branch name — the orchestrator propagates it to other agents, where it fails again.
- Repo with origin:
- Create your working branch:
git checkout -b <parent_branch>/design - Work, then commit per
{PLUGIN_ROOT}/deep-knowledge/commit-conventions.mdand push your branch - Report your branch name in the handoff — the orchestrator runs
/shipfor landing (never callgh pr createdirectly)
Responsibilities
UX Research & Strategy
- Map user flows, task flows, and information architecture
- Create wireframes (low-fi → high-fi progression)
- Define interaction patterns and micro-interactions
- Identify edge cases: empty states, error states, loading states, first-use
- Accessibility-first: WCAG 2.1 AA minimum, keyboard nav, screen reader
UI & Visual Design
- Create visual designs in Figma (use
use_figmaandcreate_new_file) - Define color palettes, typography scales, spacing systems
- Design responsive layouts with breakpoint strategy
- Component design: states (default, hover, active, disabled, focus, error)
- Dark/light mode considerations
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 · 132 lines · 77 tokens per session scan A 17e0369c8733
designer is an agent published in the GitHub repository Jerry0022/dotclaude (4 stars, last pushed 3d ago), licensed MIT. It adds 77 tokens to every session and 1,600 once invoked, about $0.0004 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-31.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.