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/commands/hermeticormus/design-mastery-claude-code/premium-landing)<a href="https://agentmods.dev/commands/hermeticormus/design-mastery-claude-code/premium-landing"><img src="https://agentmods.dev/badge/commands/hermeticormus/design-mastery-claude-code/premium-landing/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/commands/hermeticormus/design-mastery-claude-code/premium-landing"><img src="https://agentmods.dev/badge/commands/hermeticormus/design-mastery-claude-code/premium-landing.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.00019 | $0.01329 |
| Opus 5.5 | $0.00008 | $0.00532 |
| Sonnet 5.5 | $0.00004 | $0.00266 |
| Haiku 4.5 | $0.00002 | $0.00133 |
Grade A, and why
premium-landing 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 19d 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
95% identical to premium-landing — 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 — 246 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Premium Landing Page Generator
Generate premium $5k+ quality SaaS landing pages using the Define → Build → Review → Refine framework.
Usage
/premium-landing [phase] [options]
Phases
/premium-landing define- Create context artifacts (brief, mood boards, specs)/premium-landing setup- Generate style guide, PRD, and tasks/premium-landing build [section]- Build a specific section/premium-landing review- Audit current implementation/premium-landing refine [section]- Iterate on a section
Phase 1: Define
When invoked with define, guide the user through creating:
1. Project Brief
Ask for:
- What are you building?
- Who is your target audience?
- What are the goals of this landing page?
- What sections should it have?
Create: docs/project-brief.md
2. Content Files
For each section identified:
- Ask for headline, subheadline, CTAs, body copy
- Create:
docs/sections/[section-name]-content.md
3. General Vibe Mood Board
Ask for:
- Light or dark theme? Why?
- What colors resonate with your audience?
- What feeling should the site evoke?
- Any inspiration sites?
Create: docs/general-vibe.md
4. Section-Specific Mood Boards
For each section:
- Ask for layout preferences
- Component library preferences (shadcn, 21st.dev)
- Animation requirements
- 3D elements if any
Create: docs/sections/[section-name]-specs.md
Phase 2: Setup
When invoked with setup:
Generate Style Guide
Read all mood boards and brief, then create:
- Color palette with usage guidance
- Typography scale
- Spacing system
- Component patterns
- Animation guidelines
Create: docs/style-guide.md
Generate PRD
Extract from section specs:
- Tech stack needed
- Dependencies required
- File structure
- Performance requirements
Create: docs/prd.md
Generate Tasks
Based on PRD and sections:
- Phase 1: Project setup
- Phase 2: Core components
- Phase 3: Per-section build tasks
- Phase 4: Polish
- Phase 5: Launch
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.
- 19d ago First seen · 246 lines · 19 tokens per session scan A 0adc4373f885
premium-landing is a command published in the GitHub repository HermeticOrmus/design-mastery-claude-code (19 stars, last pushed 16d ago), licensed MIT. It adds 19 tokens to every session and 1,329 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 95% identical to premium-landing, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
start
Run the canvas-to-code workflow — guided discovery, auto-resume, or jump to a specific gate.
critique-ux
Run a focused UX critique on a screen — affordances, information density, and hierarchy — and output a prioritised fix list.
design-onboarding
Design a first-run experience end to end — activation path, progressive disclosure, and time to first value.
frame-problem
Structure an ambiguous design challenge into a clear problem definition with constraints and criteria.
strategize
Develop a complete UX strategy for a product or feature area.
generate-design-md
Génère un DESIGN.md à la racine du projet à partir du template Claude Craft + analyse des sources UI existantes (Tailwind, tokens, CSS).