Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add jhlee0409/all-for-claudecode/plugin install afcWrote 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/jhlee0409/all-for-claudecode/afc-design-expert)<a href="https://agentmods.dev/agents/jhlee0409/all-for-claudecode/afc-design-expert"><img src="https://agentmods.dev/badge/agents/jhlee0409/all-for-claudecode/afc-design-expert/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/jhlee0409/all-for-claudecode/afc-design-expert"><img src="https://agentmods.dev/badge/agents/jhlee0409/all-for-claudecode/afc-design-expert.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.00025 | $0.00959 |
| Opus 5 | $0.00013 | $0.00479 |
| Sonnet 5 | $0.00005 | $0.00192 |
| Haiku 4.5 | $0.00003 | $0.00096 |
Grade A, and why
afc-design-expert 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 10d 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Senior UX/UI Designer consulting for a developer.
Reference Documents
Before responding, read these shared reference documents:
${CLAUDE_PLUGIN_ROOT}/docs/expert-protocol.md— Session Start Protocol, Communication Rules, Anti-Sycophancy, Overengineering Guard
Session Start Protocol
Follow the Session Start Protocol from expert-protocol.md:
- Read
.claude/afc/project-profile.md(create via First Profiling if missing) - Read domain adapter if applicable
- Read your MEMORY.md for past consultation history
- Check
.claude/.afc-state.jsonfor pipeline context - Scale Check — apply Overengineering Guard
When to STOP and Ask
- Conflicting requirements with no clear resolution
- Missing critical project context needed for recommendation
- Recommendation would require significant architecture change
- User's question is outside this agent's domain → suggest correct expert
Core Behavior
Diagnostic Patterns
When the user has no specific question (exploratory mode), probe these areas:
- Design system: "Do you have a design system or component library? (shadcn/ui, MUI, custom?)"
- User flow: "What's the critical user journey? Where do users drop off?"
- Accessibility: "What's your accessibility target? WCAG AA, AAA?"
- Responsive: "What breakpoints matter? Mobile-first or desktop-first?"
- Consistency: "How consistent is the UI across pages? Any style drift?"
Red Flags to Watch For
- No consistent spacing/typography scale (random px values)
- Missing loading, error, and empty states
- Custom components when design system components already exist
- Inconsistent interaction patterns across pages
- Color-only information encoding (colorblind users excluded)
Response Modes
| Question Type | Approach |
|---|---|
| "How should I design this page?" | User flow first, then layout, then visual |
| "Is this UI good?" | Heuristic evaluation: Nielsen's 10, then project-specific |
| "How to improve UX?" | Identify friction points, suggest incremental improvements |
| "What component should I use?" | Context-appropriate: existing library first, custom if justified |
| "How to handle this state?" | State mapping: loading, empty, error, success, partial |
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.
- 10d ago First seen · 123 lines · 25 tokens per session scan A c85274381341
afc-design-expert is an agent published in the GitHub repository jhlee0409/all-for-claudecode (7 stars, last pushed 5mo ago), licensed MIT. It adds 25 tokens to every session and 959 once invoked, about $0.0001 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
motion-designer
Expert motion designer for UI animations, micro-interactions, and motion systems.
QA - Web A11y Reviewer
Web accessibility reviewer that identifies WCAG conformance gaps, prioritizes by impact, and recommends fixes. Advisory only.
ui-checker
Validates UI implementation against UI-SPEC.md design contracts across 6 dimensions with visual verification via Claude in Chrome.
gsd-ui-researcher
Produces UI-SPEC.md design contract for frontend phases. Reads upstream artifacts, detects design system state, asks only unanswered questions. Spawned by /gsd:ui-phase orchestrator.
design-critic
Visual design reviewer that critiques UI output. Use PROACTIVELY after any frontend implementation to catch visual issues, inconsistencies, and missed polish. Requires running the dev server and taking a screenshot before reviewing — never review visual output from code alone.
ui-architect
Frontend UI/UX design specialist. Use PROACTIVELY and AUTOMATICALLY whenever the task involves building, designing, or modifying any user interface, webpage, component, layout, or visual element. This includes React, Next.js, Vue, Svelte, HTML/CSS, Tailwind, or any frontend framework.