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 HalidSaglam/saglitzdesign-mcp --skill landing-page-conversiongit 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/skills/halidsaglam/saglitzdesign-mcp/landing-page-conversion)<a href="https://agentmods.dev/skills/halidsaglam/saglitzdesign-mcp/landing-page-conversion"><img src="https://agentmods.dev/badge/skills/halidsaglam/saglitzdesign-mcp/landing-page-conversion/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/halidsaglam/saglitzdesign-mcp/landing-page-conversion"><img src="https://agentmods.dev/badge/skills/halidsaglam/saglitzdesign-mcp/landing-page-conversion.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.00086 | $0.01332 |
| Opus 5 | $0.00043 | $0.00666 |
| Sonnet 5 | $0.00017 | $0.00266 |
| Haiku 4.5 | $0.00009 | $0.00133 |
Grade A, and why
landing-page-conversion 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 8d 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Landing Page Conversion
A beautiful page with unclear positioning converts worse than a plain page with sharp positioning. Fix upstream first: positioning → copy → structure → design → speed.
Full depth (frameworks, real examples, benchmarks) is in the SaglitzDesign MCP (
npx saglitzdesign-mcp): docsconversion-ux,storybrand-copywriting,value-proposition-jtbd,influence-persuasion,growth-frameworks,web-hero-sections; toolsaudit_ux_copy(readability, weak CTAs),create_design_system,generate_layout_system, and the/saglitzdesign:build_landing_pageworkflow.
Order of operations
- Positioning first. One sentence: for [segment] who [struggle], [product] is the [category] that [key value], unlike [alternative]. Decide the ONE conversion goal of the page.
- Value proposition. Map the customer's job-to-be-done (functional/social/emotional) to your value. This becomes the headline.
- Copy before layout. Write the real headline, subhead, CTA, and section copy before designing. Never design with lorem ipsum.
- Then design & build, then optimize.
The above-the-fold contract
In ~5 seconds a visitor must answer: What is this? Who's it for? Why care? What do I do next?
- Headline: outcome-focused, specific, ≤10 words. "Ship your app in days, not months" — not "Welcome" or "Empower your workflow."
- Subhead: 1–2 lines on how/who.
- One primary CTA, value-forward: "Start free trial", "Get the template" — never "Submit".
- Risk reducers next to it: "Free · No credit card · Cancel anytime."
- Real product visual (screenshot/video) beats abstract illustration.
- Proof strip (logos / rating / count) right under the hero.
Page narrative (proven order)
Hero (promise + CTA + proof) → problem / how-it-works (3 steps) → benefit sections (benefit-led headings, features as evidence) → deep social proof (named testimonials with faces + results) → pricing (if self-serve) → objections / FAQ → final CTA → footer.
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.
- 8d ago Changed · +18 lines b0bdbbed6896
- 12d ago First seen · 60 lines · 86 tokens per session scan A a26083c3291c
landing-page-conversion is a skill published in the GitHub repository HalidSaglam/saglitzdesign-mcp (5 stars, last pushed 10d ago), licensed MIT. It adds 86 tokens to every session and 1,332 once invoked, about $0.0004 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 skills, from other repositories
bridge-troubleshooting
Diagnose figma-mcp-rust connection problems. Use when tools fail with "plugin not connected", requests time out, the port is already in use, or the Figma plugin cannot reach the MCP server. Covers installing the companion Figma plugin, port 1994, and running multiple MCP clients.
logo-creator
Create logos using AI image generation. Discuss style/ratio, generate variations, iterate with user feedback, crop, remove background, and export as SVG. Use when user wants to create a logo, icon, favicon, brand mark, mascot, emblem, or design a logo.
api-errors
McpError constructor, JsonRpcErrorCode reference, and error handling patterns for @cyanheads/mcp-ts-core. Use when looking up error codes, understanding where errors should be thrown vs. caught, or using ErrorHandler.tryCatch in services.
conversational-ux
Design voice and conversational interfaces — dialog flows, error recovery, and persona. Use when the interface speaks and listens rather than being tapped. For graphical input collection, use form-design.
design-negotiation
Advocate for design quality, scope, and timeline with partners and leadership using evidence and shared goals. Use in the conversation itself. For the commercial vocabulary behind it, use business-design (ux-strategy).
platform-conventions
Design to iOS and Android conventions — what each OS mandates, where they diverge, and when to unify. Use when shipping native apps. For breakpoint adaptation use responsive-design; for matching competitor patterns use jakobs-law (interaction-design).