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 skills add HermeticOrmus/design-mastery-claude-code --skill premium-saas-designgit 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/skills/hermeticormus/design-mastery-claude-code/premium-saas-design)<a href="https://agentmods.dev/skills/hermeticormus/design-mastery-claude-code/premium-saas-design"><img src="https://agentmods.dev/badge/skills/hermeticormus/design-mastery-claude-code/premium-saas-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.
<a href="https://agentmods.dev/skills/hermeticormus/design-mastery-claude-code/premium-saas-design"><img src="https://agentmods.dev/badge/skills/hermeticormus/design-mastery-claude-code/premium-saas-design.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.00071 | $0.03388 |
| Opus 5.5 | $0.00028 | $0.01355 |
| Sonnet 5.5 | $0.00014 | $0.00678 |
| Haiku 4.5 | $0.00007 | $0.00339 |
Grade A, and why
premium-saas-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 22d 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
91% identical to premium-saas-design — 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 — 571 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Premium SaaS Design Framework
In Stanford's large 2002 web credibility study (B.J. Fogg and colleagues), a site's visual design was the factor people mentioned most often when they judged whether to trust it.
This skill captures the professional design workflow used by senior product teams and UI/UX designers, adapted for AI-assisted development. The framework transforms AI from a "guessing machine" into a true design partner.
The Core Loop
DEFINE → BUILD → REVIEW → REFINE
↑ │
└────────────────────────┘
This loop is everything. It's used by real product teams and works wonders with AI.
The 7 Context Artifacts
AI needs context to produce premium results. These 7 documents form your "design contract" with AI:
1. Project Brief
What: Single document explaining what you're building, why, and for whom. Purpose: Gives AI direction and understanding of the project.
# Project Brief: [Product Name]
## What We're Building
[Description of the product/website]
## Primary Target Audience
- [Persona 1]: [Description]
- [Persona 2]: [Description]
## Goals
1. [Primary goal - e.g., drive signups]
2. [Secondary goal - e.g., build trust]
3. [Tertiary goal - e.g., explain the product]
## Requirements
- Fully responsive (mobile-first)
- Blazing fast performance
- Accessible (WCAG 2.1 AA)
- [Other requirements]
## Sections
1. Hero
2. Trust Logos
3. Features
4. [etc.]
Key Insight: Think of AI as a new team member. You wouldn't tell them "build me a website" without context.
2. Content Files (One Per Section)
What: Separate file for each section containing all copy/content. Purpose: Focuses AI on content separately from design.
# Hero Section Content
## Headline
[Main headline text]
## Subheadline
[Supporting text]
## CTA Primary
Text: [Button text]
Action: [What happens on click]
## CTA Secondary
Text: [Link text]
Action: [What happens on click]
## Social Proof (optional)
[Trust indicators, stats, etc.]
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.
- 22d ago First seen · 571 lines · 71 tokens per session scan A 5f22308243dc
premium-saas-design is a skill published in the GitHub repository HermeticOrmus/design-mastery-claude-code (19 stars, last pushed 18d ago), licensed MIT. It adds 71 tokens to every session and 3,388 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 91% identical to premium-saas-design, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
anti-slop-design
Autonomous Principal Design Technologist. Cures vibe-coded software from AI frontend slop using curated token archetypes and 7-axis quality gating.
figma-extract-design-system
Extract a design system from vibe-coded production apps that never had one: inventory components, mine de-facto styling into DTCG tokens, scaffold a Storybook package, port components, and optionally round-trip tokens/components into Figma. Use when the user wants to 'extract a design system', 'create a design system…
figma-blame-node
Find which Figma version introduced a specific change — a component property or a child node — via a binary search over version history (log2(N) API calls instead of N). Answers 'who added this and when'. Use when the user wants git-blame-style attribution for a Figma design — triggers: 'when was this component…
figma-generate-component-doc
Generate complete Markdown documentation for a Figma component — anatomy/layer tree, design tokens (colors, spacing, typography), states/variants matrix, accessibility notes, content guidelines, and optional code-parity + YAML frontmatter. Use when the user wants a docs page or handoff spec for a component or…
figma-version-history
List a Figma file's version history, snapshot the file at any past version, and diff two versions (added/removed/renamed pages plus deep per-component changes). Use when the user wants to inspect Figma history — triggers: 'list Figma versions', 'what versions does this file have', 'show version history', 'snapshot…
figma-comments
Read, post, reply to, and delete comments on a Figma file via the REST API — including pinning a comment to a specific node and threading replies. Use when the user wants to work with Figma comments programmatically — triggers: 'get Figma comments', 'read comments on this file', 'post a comment in Figma', 'leave a…