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/HalidSaglam/saglitzdesign-mcpWrote 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/halidsaglam/saglitzdesign-mcp/build_website)<a href="https://agentmods.dev/commands/halidsaglam/saglitzdesign-mcp/build_website"><img src="https://agentmods.dev/badge/commands/halidsaglam/saglitzdesign-mcp/build_website.svg" alt="Measured on agentmods" 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.00033 | $0.02506 |
| Opus 5 | $0.00016 | $0.01253 |
| Sonnet 5 | $0.00007 | $0.00501 |
| Haiku 4.5 | $0.00003 | $0.00251 |
Grade A, and why
build_website 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 2d 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
86% identical to build_landing_page — 21 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Build a marketing website, using the SaglitzDesign method.
You have the SaglitzDesign tools available. Use them — do not design from memory.
Knowledge (judgement):
- get_design_roadmap(project_type) — the phased plan; call FIRST on any build.
- search_design_knowledge(query) / get_design_doc(id) — rules & specs. Ids also readable as saglitzdesign://doc/{id}.
- get_component_guidance(component, platform) — per-component specs + patterns.
- get_design_language(language) — Material 3 / Liquid Glass / iOS / Android / macOS / visionOS / Fluent / web-trends / tokens.
- compare_design_languages(topic, platforms) — how each platform solves one surface, and what NOT to port.
- get_design_examples(query, platform) — curated real-world example screens.
- seo_geo_guide(scope, topic) — SEO & GEO for web.
Generators (real output, not advice — prefer these over inventing values):
- create_design_system(brand_color, vibe, platform) — the one-call foundation: direction card + color + fonts + icons + type scale + elevation + tokens + component list.
- generate_layout_system(preset) — breakpoints, containers, grid, container queries, section rhythm.
- generate_color_system / suggest_font_pairing / suggest_icon_library / generate_type_scale / generate_elevation_system / generate_motion / generate_design_tokens — the individual layers.
- get_component_recipe(component, stack) — production-ready accessible code for button/input/modal/toast/card/switch/tabs/empty-state/list-row/navigation/search/select/table/tooltip/form/pagination/skeleton/badge/breadcrumb.
- fix_contrast(foreground, background, target) — the corrected color value, not just a fail report.
Auditors (deterministic gates — run these before claiming done):
- audit_accessibility(contrast_pairs, tap_targets) — exact WCAG ratios and target sizes.
- design_lint(code) — design & a11y anti-patterns with line numbers.
- audit_design_system(code) — consistency score + value sprawl across the whole codebase.
- audit_project(path) — the same auditors over a real directory instead of a pasted snippet, ranked worst-file-first. Prefer this when you have the source on disk.
- audit_generic_design(code) — the specific defaults generated interfaces reach for (stock indigo/violet/purple gradient, Inter as the only family, the rounded-2xl card recipe, gradient headings, eyebrow-on-every-heading, three or more animate-pulse/shimmer placeholders). Facts about source, not taste. A genuine indigo brand still flags.
- audit_ux_copy(text) — readability, passive voice, jargon, weak CTAs.
- audit_ethical_design(code) — named deceptive-pattern tells in a pasted snippet (confirmshaming decline copy, a pre-checked marketing checkbox, literal scarcity/deadline copy with no live binding, Accept all without Reject all). Facts about source, not a verdict. Pair with get_design_doc("ethical-design").
- audit_apple_ui(path) — iOS/macOS project directory. Reads configuration and Swift. Directory only; no snippet mode.
- audit_android_ui(path) — Android project directory. Reads the manifest, resource XML and Compose. Directory only; no snippet mode.
- measure_screenshot(path, scale, format) — measures a PNG screenshot's real palette, contrast ratios, density and structure, and names a stock-region fact when a significant cluster sits in Tailwind indigo/violet/purple. Use it whenever you have an image file rather than source.
- design_review_checklist(project_type, focus) — the assembled audit checklist.
Sequence
- Call get_design_roadmap("website") and follow its phases (positioning → copy → IA/SEO → design → build → CRO).
- Positioning + IA first. Ask me up to 4 questions if the audience, offer, conversion goal, page set or brand color is unclear. Then propose a sitemap (home, product/features, pricing, about, contact…), each page mapped to one search intent. get_design_doc("information-architecture") for the structure.
- Copy before layout for each page (get_design_doc("storybrand-copywriting"), get_design_doc("marketing-website-roadmap")); audit_ux_copy each page's headline and primary CTA.
- SEO/GEO foundations up front: seo_geo_guide("both") — rendering, meta, schema plan, llms.txt, internal linking.
- Reference real examples via get_design_examples for each section type.
- Generate the foundation ONCE (below) and share it across every page — that is what makes a multi-page site feel like one product. Layout preset "marketing-site".
- Build it as a coherent multi-page site (default: static HTML/CSS with shared styles, or a Next.js app if I ask). Shared tokens; consistent nav/footer; every page in all states. Use get_component_recipe for repeated components.
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.
- 2d ago Changed · +8 lines ada79b9daa91
- 6d ago First seen · 99 lines · 33 tokens per session scan A f74c3e4bc8e8
build_website is a command published in the GitHub repository HalidSaglam/saglitzdesign-mcp (4 stars, last pushed 5d ago), licensed MIT. It adds 33 tokens to every session and 2,506 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to build_landing_page, differing in 21 lines, and is treated as a copy.
Other commands, from other repositories
map-states
Model a component's states and transitions end to end — states, events, guards, and edge cases.
color-palette
Run the full colour workflow — tonal scales, semantic mapping, contrast checks, dark mode, and chart colours — and output a documented palette.
design-screen
Design a complete screen layout from a description or requirements.
responsive-audit
Audit a design's responsive behaviour across breakpoints — layout, touch targets, and content reflow.
type-system
Build a typography system end to end — scale, weights, line heights, measure, and responsive behaviour.
critique-ux
Run a focused UX critique on a screen — affordances, information density, and hierarchy — and output a prioritised fix list.