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 commands/hermeticormus/design-mastery-claude-code/brand-identitygit clone --depth 1 https://github.com/HermeticOrmus/design-mastery-claude-codeWhat 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.00028 | $0.01458 |
| Opus 5 | $0.00014 | $0.00729 |
| Sonnet 5 | $0.00006 | $0.00292 |
| Haiku 4.5 | $0.00003 | $0.00146 |
Grade A, and why
brand-identity 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.
How it starts
The opening of the file, as written. The whole thing — 247 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Brand Identity Builder
You are guiding the user through systematic brand identity development.
Phase Detection
First, determine where the user is in their brand journey:
- Starting Fresh: No brand exists yet
- Clarifying: Brand exists but needs refinement
- Rebranding: Major change needed
- Extending: Adding to existing system
Workflow Phases
Phase 1: Discovery (5-10 questions)
Ask these in conversation, not as a list:
Business Foundation
- What problem does your business solve?
- Who are you solving it for?
- Why did you start this?
Competitive Landscape
- Who are your main competitors?
- What do they do well?
- What do they get wrong?
Aspirational Direction
- What brands do you admire (any industry)?
- If your brand were a person, how would they act?
- What should people feel when they encounter your brand?
Phase 2: Strategy Synthesis
Based on discovery, create:
## Brand Strategy Summary
### Positioning Statement
For [target audience]
Who [need/problem]
[Brand name] is a [category]
That [key benefit]
Unlike [competitors]
We [key differentiator]
### Brand Personality
1. [Attribute 1] - [What this means in practice]
2. [Attribute 2] - [What this means in practice]
3. [Attribute 3] - [What this means in practice]
### Core Values
1. [Value 1] - [How this shows up]
2. [Value 2] - [How this shows up]
3. [Value 3] - [How this shows up]
### Brand Archetype
Primary: [Archetype]
Secondary: [Archetype]
Voice implications: [How this affects communication]
Phase 3: Visual Direction
Present 2-3 distinct visual directions:
## Direction A: [Name]
**Mood**: [Adjectives]
**Reference movements**: [Historical context]
**Color family**: [Palette description]
**Typography feel**: [Type personality]
**Why it fits**: [Connection to strategy]
## Direction B: [Name]
...
## Direction C: [Name]
...
For each direction, provide sample CSS/Tailwind:
/* Direction A: [Name] */
:root {
/* Primary */
--color-primary: #XXXXXX;
--color-primary-hover: #XXXXXX;
/* Accent */
--color-accent: #XXXXXX;
/* Neutrals */
--color-text: #XXXXXX;
--color-text-muted: #XXXXXX;
--color-background: #XXXXXX;
--color-surface: #XXXXXX;
/* Typography */
--font-display: 'FontName', sans-serif;
--font-body: 'FontName', sans-serif;
}
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.
- yesterday First seen · 247 lines · 28 tokens per session scan A b619a535ff41
brand-identity is a command published in the GitHub repository HermeticOrmus/design-mastery-claude-code (11 stars, last pushed 3mo ago), licensed MIT. It adds 28 tokens to every session and 1,458 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-30.
Other commands, from other repositories
build_landing_page
Design & build a conversion-focused landing page end-to-end using SaglitzDesign expertise — generated design system, real code, deterministic audit gate, visual critique loop.
port_to_platform
Take an existing design or implementation to another platform (iOS ↔ Android ↔ macOS ↔ web) — porting the intent and IA, not the components.
redesign
Improve an existing UI (bolder, quieter, cleaner, higher-converting) using SaglitzDesign craft standards, with measured before→after.
critique_screenshot
Grounded, reproducible visual critique of an attached UI screenshot against the fixed 0–40 rubric — cites specific elements, no padding.
design_review
Audit an existing website / app / landing page against SaglitzDesign checklists, the deterministic auditors, and the 0–40 critique rubric.
review_paywall
Score a paywall or subscription onboarding against real RevenueCat 2026 conversion benchmarks and paywall-anatomy rules.