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 Uxcel-Lab/product-skills --skill landing-pagegit clone --depth 1 https://github.com/Uxcel-Lab/product-skillsWrote 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/uxcel-lab/product-skills/landing-page)<a href="https://agentmods.dev/skills/uxcel-lab/product-skills/landing-page"><img src="https://agentmods.dev/badge/skills/uxcel-lab/product-skills/landing-page/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/uxcel-lab/product-skills/landing-page"><img src="https://agentmods.dev/badge/skills/uxcel-lab/product-skills/landing-page.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.00123 | $0.02485 |
| Opus 5 | $0.00062 | $0.01242 |
| Sonnet 5 | $0.00025 | $0.00497 |
| Haiku 4.5 | $0.00012 | $0.00248 |
Grade A, and why
ux-landing-page 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 11d 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Landing Page Skill
How this skill behaves (read first)
This is a generative skill, and a landing page has exactly one job: move the visitor toward a single conversion goal. The default failure is the everything page — full site nav, several competing offers, a vague headline, walls of copy, and a CTA you have to scroll to find — so attention scatters and nobody converts. (Users form a first impression in ~0.05s and read as little as ~20% of the copy.) The opposite failure is a beautiful hero with no value proposition and no reason to trust it. So this skill gates:
- Establish the single conversion goal and who's arriving — that decides what stays on the page and what gets cut.
- Apply the always-true core — one focus, a sharp headline, an obvious value proposition, a prominent CTA, trust signals, fast and responsive.
- Surface the context-dependent decisions (cut vs. keep nav, perks, chat, scroll length) with trade-offs.
Then it hands off to ux-aesthetics-audit, ux-heuristics-audit, ux-accessibility-audit, ux-microcopy-audit, ux-dark-patterns-audit, and ux-mobile-responsiveness-audit for validation.
Scope & composition (per docs/orchestration-policy.md §9): this skill covers the landing page itself and composes lower-scope skills rather than re-deriving them. Core children (built as part of the page): CTA button mechanics via ux-buttons. Downstream (offer, don't auto-build): pricing tables via ux-pricing and the post-click sign-up/checkout via ux-login-signup and ux-checkout-payment. Inherit, don't regenerate: under an existing design system, take color/type/spacing from its tokens — only set those when designing from scratch.
Step 0 — Establish context before designing
Ask if not known; state the assumption if proceeding without an answer:
- What's the single conversion goal? Sign up, buy, book a demo, subscribe, download. One page, one primary action — everything else is subordinate. If stakeholders want several goals, that's a prioritization conversation, not five equal buttons.
- Who's arriving, and how aware are they? A specialized audience tolerates (some) domain terms; a general or top-of-funnel audience needs plain language and more context before the ask. Traffic source (an ad for one feature vs. a homepage) shapes how tightly the page must match the promise that brought them.
- Campaign landing page vs. a page within the site? A dedicated campaign page often removes global nav to protect focus; a page inside the main site usually keeps it for wayfinding. This single choice flips several defaults.
- Product type & brand — bounds image style, tone, and whether playful copy fits.
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.
- 11d ago First seen · 115 lines · 123 tokens per session scan A 261154d49fe8
ux-landing-page is a skill published in the GitHub repository Uxcel-Lab/product-skills (10 stars, last pushed 2mo ago), licensed MIT. It adds 123 tokens to every session and 2,485 once invoked, about $0.0006 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
pm-brand-motion
A guided process for defining a brand's motion style and making a logo animation demonstration.
pm-proto
A product-prototyping workflow for planning how an application should work and what its screens should contain. It connects product requirements to interface layouts and interactions.
diagram-design
Create branded architecture, IT current-state, flowchart, sequence, state machine, ER/data model, timeline, swimlane, quadrant, radar/spider, polar chart (polar/radial lollipop), loop/flywheel, nested, tree, org chart, layer stack, Venn, pyramid/funnel, treemap, bar, line, Gantt and scatter charts, high-level…
design-mobile-apps
Use when the user wants to design a mobile app or UI screens, when they mention their Sleek (sleek.design) projects, or when implementing Sleek designs in code (HTML, React Native, SwiftUI).
dengguang-zhaoming-bikeng-zhinan
A Chinese-language knowledge guide about home lighting, including ceiling lights, light strips, color temperature, color rendering, and room zoning.
appllama-app-design-skill
Build native-feeling, benchmark-quality mobile app screens (Expo / React Native). Use when designing or implementing any mobile UI — screens, flows, onboarding, paywalls, tab bars, sheets, settings, empty states — or when polishing motion, navigation, typography, dark mode, or perceived performance. Enforces Apple HIG…