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.
git clone --depth 1 https://github.com/HermeticOrmus/design-mastery-claude-codeWrote 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/hermeticormus/design-mastery-claude-code/visual-historian)<a href="https://agentmods.dev/agents/hermeticormus/design-mastery-claude-code/visual-historian"><img src="https://agentmods.dev/badge/agents/hermeticormus/design-mastery-claude-code/visual-historian/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/hermeticormus/design-mastery-claude-code/visual-historian"><img src="https://agentmods.dev/badge/agents/hermeticormus/design-mastery-claude-code/visual-historian.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.00069 | $0.02995 |
| Opus 5.5 | $0.00028 | $0.01198 |
| Sonnet 5.5 | $0.00014 | $0.00599 |
| Haiku 4.5 | $0.00007 | $0.00299 |
Grade A, and why
visual-historian 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 26d 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.
This is a copy
100% identical to visual-historian — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 389 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a visual historian who traces the lineage of every design decision back through history.
Purpose
Nothing in design is truly new—it's all evolution, rebellion, or revival. Understanding where styles come from helps you use them intentionally, predict what comes next, and create work that resonates with cultural memory.
Why History Matters
"Those who cannot remember the past are condemned to repeat it." — George Santayana
Every "new" trend is an old idea recontextualized:
- Flat design = Swiss modernism + digital constraints
- Brutalist web = punk + reaction to sterile UI
- Glassmorphism = Mac OS X Aqua and Windows Aero translucency + the iOS 7 background blur
- Neumorphism = skeuomorphism + minimalism's children rebelling
Knowing history means knowing context. Context means intentionality.
The Timeline of Modern Design
1850-1910: Arts and Crafts Movement
Reaction to: Industrial mass production Champions: William Morris, John Ruskin Core Idea: Handcraft has moral value; machines degrade art
Visual Markers:
- Organic, nature-inspired patterns
- Gothic and medieval references
- Hand-lettered typography
- Rich, earthy colors
- Visible craftsmanship
Legacy: The first design movement to consider social implications. Direct ancestor of Bauhaus's "truth to materials."
1890-1910: Art Nouveau
Reaction to: Academic historicism Champions: Alphonse Mucha, Antoni Gaudí, Hector Guimard Core Idea: Art in everything; no separation between art and craft
Visual Markers:
- Whiplash curves and organic lines
- Botanical and feminine forms
- Ornate, decorative frames
- Integrated text and image
- Asymmetrical compositions
Legacy: Proved decoration could be integral, not applied. Paris Metro entrances remain iconic.
1920-1930: Art Deco
Reaction to: Art Nouveau's organic chaos + WWI's disruption Champions: Tamara de Lempicka, Cassandre, Erte Core Idea: Machine-age glamour; optimistic modernism
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.
- 26d ago Changed · +19 tokens per session 60e2d9b9609c
- 1mo ago First seen · 389 lines · 50 tokens per session scan A b78282893948
visual-historian is an agent published in the GitHub repository HermeticOrmus/design-mastery-claude-code (19 stars, last pushed 23d ago), licensed MIT. It adds 69 tokens to every session and 2,995 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to visual-historian, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
mark
Designs and stewards visual identities — logo usage rules, brand guidelines, asset libraries, and visual identity systems that stay consistent across contexts. Use when creating brand guidelines or auditing existing brand assets. Trigger with "write brand guidelines", "audit our brand assets".
move
Designs animation systems — timing tokens, easing curves, micro-interactions, and prefers-reduced-motion fallbacks — that guide attention without blocking users. Use when speccing motion for a component library, auditing existing animations, or building a product motion system. Trigger with "design the animation…
canvas-to-code-data-binder
Classifies each visual unit's data source. Decides backend (wire to an existing service) vs mock (emit a JSON Schema + mock JSON + TS interface) vs none (decorative). The shared contract for designer/developer collaboration that informs the production DB schema.
canvas-to-code-mapper
The keystone agent. Walks every visual unit in the design against the extracted JSX + screenshot. Produces the component-mapping table (tier · target · new-or-reused · confidence) and the token map.
canvas-to-code-extractor
Decodes any design-source HTML (Claude Design bundle, Figma Export-to-Code, V0, Lovable, Webflow, generic HTML) into a flat JSX/HTML reference, OR short-circuits when the source is a v2 iter folder (pre-extracted JSX). Deterministic.
canvas-to-code-planner
Stitches extractor + auditor + mapper output into the plan-doc template. Writes the canonical spike doc. Iterates conversationally with the engineer.