head-of-design

head-of-design is an agent for Claude Code from me2resh/apexyard. It costs 39 tokens per session (472 once invoked), scanned A, original, MIT.

An AI role responsible for a product’s design system, user experience principles, and visual standards. A design system is the shared set of interface patterns and rules used across products.

In plain words
What is it for?
Use it when changing a design system, deciding user-experience principles, or making visual-standard decisions that affect multiple projects.
Why use it?
It gives design-related decisions a clear owner and keeps visual and user-experience choices consistent across projects.

Agent for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: model in frontmatter; mentions subagents; mentions Claude Code.

Good fit Use it when changing a design system, deciding user-experience principles, or making visual-standard decisions that affect multiple projects.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/me2resh/apexyard/head-of-design
Install

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.

Clone the repo
git clone --depth 1 https://github.com/me2resh/apexyard

Made for: Claude Code.

Wrote 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.

agentmods badge for head-of-design

README.md
[![agentmods](https://agentmods.dev/badge/agents/me2resh/apexyard/head-of-design/github.svg)](https://agentmods.dev/agents/me2resh/apexyard/head-of-design)
Your own site
<a href="https://agentmods.dev/agents/me2resh/apexyard/head-of-design"><img src="https://agentmods.dev/badge/agents/me2resh/apexyard/head-of-design/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.

agentmods 80×15 button for head-of-design

Your own site · 80×15
<a href="https://agentmods.dev/agents/me2resh/apexyard/head-of-design"><img src="https://agentmods.dev/badge/agents/me2resh/apexyard/head-of-design.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 39 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 472 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00039 $0.00472
Opus 5 $0.00019 $0.00236
Sonnet 5 $0.00008 $0.00094
Haiku 4.5 $0.00004 $0.00047

Measured yesterday against content hash 39b04eac3b5e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

head-of-design 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 yesterday.

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.

.claude/agents/head-of-design.md · 32 lines

What it actually says

Maha — Head of Design

Read and adopt @roles/design/head-of-design.md for full identity, responsibilities, CAN / CANNOT boundaries, and handoff rules. The role file is the canonical persona definition; this file is the thin runtime wrapper that owns model + tool-restriction + agent metadata only.

Activation context

This agent activates per .claude/rules/role-triggers.md — auto-triggers on the conditions listed in that file's trigger table, plus prompted activation ("act as Head of Design"). The ## Activation mode section in the role file determines whether activation spawns this sub-agent (isolated-work-class) or adopts the persona in-thread (in-flow-class). See AgDR-0050 § Axis 6 for the design.

Browser evidence is a named deliverable

Render the component before you review it. An escalation review that only reads source cannot see spacing, contrast, overflow, empty states, and loading states. Reject a PASS whose evidence does not match the criterion.

Report the browser-verification status of every design criterion. The not-verified list is mandatory: if you could not render the component, say so and name every affected criterion.

Use a browser-automation MCP server, such as Playwright MCP, when the operator has granted one. If no browser MCP server is available, do not improvise with a headless-browser CLI: report the affected criteria as not browser-verified.

Prefer an accessibility-tree snapshot over a screenshot when asserting what a component says. If you take a screenshot, wait until the page settles — a transition captured at frame 0 produces a confident, wrong finding.

Full requirement: @roles/design/head-of-design.md § "Browser evidence is a named deliverable". This applies to UI work only.


Part of ApexYard — multi-project SDLC framework for Claude Code · MIT.

Changes

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.

  1. yesterday Changed · +12 lines 39b04eac3b5e
  2. 13d ago First seen · 20 lines · 39 tokens per session scan A bbf60eafe96c

Subscribe to this mod's changes

head-of-design is an agent published in the GitHub repository me2resh/apexyard (498 stars, last pushed today), licensed MIT. It adds 39 tokens to every session and 472 once invoked, about $0.0002 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.

Related

Other agents, from other repositories

ux-flow-auditor

Use this agent when the user mentions UX flow issues, dead-end views, dismiss traps, missing empty states, broken user journeys, or wants a UX audit of their iOS app. Automatically scans SwiftUI and UIKit code for user journey defects - detects dead ends, dismiss traps, buried CTAs, missing loading/error/empty states…

CharlesWiltgen/Axiom · 190 tokens

ijfw-accessibility-reviewer

Design-phase WCAG 2.1 AA review of UI artefacts: contrast, semantics, focus, ARIA. Trigger per design review pass.

FerroxLabs/ijfw · 37 tokens

Design System Auditor

Design system accessibility auditor. Validates color tokens, CSS custom properties, Tailwind config, and design token files (Style Dictionary, tokens.json) for WCAG AA/AAA contrast compliance. Catches contrast failures at the token source before they reach deployed UI. Also validates focus ring tokens (WCAG 2.4.13…

Community-Access/accessibility-agents · 109 tokens

design

Design system generator — maps product domain to style, palette, typography, anti-patterns. Creates .rune/design-system.md. Use BEFORE any frontend code generation.

Rune-kit/rune · 35 tokens

mobile-ux-optimizer

Use this agent when you need to optimize UI/UX components or interfaces for mobile-first experiences, analyze existing design themes, or ensure mobile usability standards are met. Examples: Context: User has created a desktop-focused component and needs it optimized for mobile. user: 'I've built this navigation…

xbim08/awesome-claude-code-plugins · 0 tokens

frontend-reviewer

Reviews interface, branding and copy. Always verifies against a screenshot and the rendered DOM, never by reading CSS or HTML.

everywan-dev/claude-code-engineering · 28 tokens