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/port_to_platform)<a href="https://agentmods.dev/commands/halidsaglam/saglitzdesign-mcp/port_to_platform"><img src="https://agentmods.dev/badge/commands/halidsaglam/saglitzdesign-mcp/port_to_platform.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.00035 | $0.02076 |
| Opus 5 | $0.00017 | $0.01038 |
| Sonnet 5 | $0.00007 | $0.00415 |
| Haiku 4.5 | $0.00003 | $0.00208 |
Grade A, and why
port_to_platform 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Port this UI to another platform, 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.
The rule this workflow exists to enforce
Share the intent, the information architecture and the content; re-implement every control natively. A product that feels native everywhere ported decisions, not components. A Material top app bar on iOS, or an iOS segmented control on Android, is the failure this prevents.
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.
- 4d ago Changed · +8 lines f821760f27eb
- 8d ago First seen · 78 lines · 35 tokens per session scan A 9b0854bc3d99
port_to_platform is a command published in the GitHub repository HalidSaglam/saglitzdesign-mcp (5 stars, last pushed 6d ago), licensed MIT. It adds 35 tokens to every session and 2,076 once invoked, about $0.0002 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-31.
Other commands, from other repositories
platform-audit
Audit a design for iOS and Android convention compliance — navigation, controls, typography, and platform-specific gaps.
start-here
Find where to start in the collection — name what you're working on and get routed to one command, the two that follow it, and the stages you can skip.
critique-screen
Run all seven visual critiques on a screen and output a prioritised fix list.
explore-options
Run a parallel exploration end to end — frame the decision, build a spread of behaviourally distinct concepts, pressure-test each, and converge with a decision record.
critique-ux
Run a focused UX critique on a screen — affordances, information density, and hierarchy — and output a prioritised fix list.
handoff
Run the full handoff workflow — specs, measurements, assets, states, and a QA checklist — and output a developer-ready package.