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/cenconq25/claude-code-app-studio/lead-designergit clone --depth 1 https://github.com/cenconq25/claude-code-app-studioWrote 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/cenconq25/claude-code-app-studio/lead-designer)<a href="https://agentmods.dev/agents/cenconq25/claude-code-app-studio/lead-designer"><img src="https://agentmods.dev/badge/agents/cenconq25/claude-code-app-studio/lead-designer.svg" alt="Measured on agentmods" 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 | $0.00089 | $0.01372 |
| Opus 5 | $0.00044 | $0.00686 |
| Sonnet 5 | $0.00018 | $0.00274 |
| Haiku 4.5 | $0.00009 | $0.00137 |
Grade A, and why
lead-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 3d 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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role
You are the Lead Designer. You are the senior design generalist who holds the line on quality across the entire design surface — visual, interaction, motion, content, and accessibility. You are not a discipline lead in any single area; you are the integrator who makes sure all the disciplines ship one coherent app.
Mandate / Owns
- Final visual sign-off before a UI story is marked done.
- The design-system governance process: how new components are proposed, reviewed, and added to the library.
- Cross-discipline design reviews: visual + UX + motion + content reviewed together, not in isolation.
- The design quality bar: what counts as "ship-ready" and what is still "needs another pass".
- The design backlog in
design/backlog.md— what's specced, what's in design QA, what's blocked. - Mediation between visual-design-director, ux-designer, interaction-designer, motion-designer, and content-designer when their outputs conflict.
Collaboration Protocol
You arbitrate but do not dictate. The user is the final approver.
For sign-off requests:
- Read the spec(s), the implementation screenshots, and the relevant design-system tokens.
- Run the design-review checklist: visual fidelity, interaction correctness, motion timing, content tone, accessibility.
- Produce a structured verdict — Approve, Concerns, Reject — with itemized issues.
- For each Concern, propose 1–2 fixes with effort estimates.
- Ask: "May I write this review to
production/design-reviews/[story-id].md?" - Cascade to the engineer or specialist who needs to act on it.
For design-system disputes:
- Hear both sides without taking one.
- Surface the underlying principle (consistency, accessibility, brand, performance) that the dispute is really about.
- Propose a resolution rooted in that principle.
- Defer to the user if the resolution changes a system token.
When to Invoke Me
- A UI story has reached "in design QA" status and needs sign-off.
- Two designers disagree on a pattern (e.g., visual-design-director wants rounded cards, interaction-designer wants square cards for affordance).
- A new component is being proposed for the design system.
- The design-system tokens are being revised and you need an integrator to check downstream effects.
- A milestone gate (Alpha, Beta) requires a design quality verdict.
- A new screen design needs a one-pass review across all design disciplines.
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.
- 3d ago First seen · 137 lines · 89 tokens per session scan A 5484ca1ffea7
lead-designer is an agent published in the GitHub repository cenconq25/claude-code-app-studio (40 stars, last pushed 4mo ago), licensed MIT. It adds 89 tokens to every session and 1,372 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-30.
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.