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 mfwarren/entrepreneur-claude-skills --skill landing-pagesgit clone --depth 1 https://github.com/mfwarren/entrepreneur-claude-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/mfwarren/entrepreneur-claude-skills/landing-pages)<a href="https://agentmods.dev/skills/mfwarren/entrepreneur-claude-skills/landing-pages"><img src="https://agentmods.dev/badge/skills/mfwarren/entrepreneur-claude-skills/landing-pages/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/mfwarren/entrepreneur-claude-skills/landing-pages"><img src="https://agentmods.dev/badge/skills/mfwarren/entrepreneur-claude-skills/landing-pages.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.00002 | $0.00587 |
| Opus 5 | $0.00001 | $0.00293 |
| Sonnet 5 | $0.00000 | $0.00117 |
| Haiku 4.5 | $0.00000 | $0.00059 |
Grade A, and why
landing-pages 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 13d 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Landing Pages
High-converting landing page wireframes, copy, and CRO recommendations.
Purpose
Create landing page structures that convert visitors into leads or customers. Combine persuasive copy with proven layout patterns.
Workflow
Step 1: Gather Context
- Goal: lead capture, product sale, sign up, demo request
- Traffic source: paid ads, organic, email, social
- Target audience
- Key offer/value prop
- Current conversion rate (if exists)
Step 2: Page Structure
Standard high-converting layout:
- Hero Section: Headline + subheadline + CTA + social proof
- Problem Section: Agitate the pain they're experiencing
- Solution Section: How your product solves it (benefits, not features)
- Social Proof: Testimonials, logos, case study snippets, numbers
- How It Works: 3-step process (simplify complexity)
- Features/Benefits: What they get (benefit-led, not feature-led)
- Pricing/Offer: Clear pricing or offer details
- FAQ: Address top 5 objections
- Final CTA: Repeat the primary call to action
- Risk Reversal: Guarantee, free trial, easy cancellation
Step 3: Write the Copy
For each section, write:
- Headline and body text
- CTA button text (action-specific: "Start free trial" not "Submit")
- Supporting copy (testimonial suggestions, proof points)
Step 4: CRO Recommendations
- Remove navigation (for dedicated landing pages)
- Single CTA — don't offer multiple paths
- Mobile-first copy (short paragraphs, large buttons)
- Speed recommendations
- Trust signals placement
Output Format
## Landing Page: [Product/Offer]
### Wireframe
[Section-by-section structure with copy]
### Hero
**Headline:** [text]
**Subheadline:** [text]
**CTA:** [button text]
[Continue for each section]
### CRO Checklist
[Optimization recommendations]
Constraints
- No navigation links on conversion-focused landing pages
- One CTA per page (can repeat, but same action)
- Don't overload with content — every section must earn its place
- Note where the user needs to provide real testimonials/logos
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.
- 13d ago First seen · 89 lines · 2 tokens per session scan A 7dac85a19ce5
landing-pages is a skill published in the GitHub repository mfwarren/entrepreneur-claude-skills (67 stars, last pushed 7mo ago), licensed MIT. It adds 2 tokens to every session and 587 once invoked, about $0.0000 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-30.
Other skills, from other repositories
frontend-design
Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.
visual-plan
Turn ordinary text plans into rich interactive visual plans with diagrams, file maps, annotated code, open questions, and UI/prototype review when useful.
visual-edit
Open a running local app in Design overview mode as URL-backed iframe screens for visual editing, flow review, duplication, and route-state exploration. Use when the user asks to inspect, compare, or edit a real local app visually in Design.
muapi-ui-design
Generate high-fidelity UI/UX mockups for mobile and web apps using Atomic Design principles — creates wireframes and design systems via muapi.ai.
display-glasses-with-jetpack-compose-glimmer
Provides guidelines for developing projected Android XR apps for display glasses using the Jetpack Compose Glimmer UI toolkit. This skill covers foundational Glimmer design principles, workflows for implementing Jetpack Compose Glimmer, and interaction models for the glasses form factor. Use this skill to build an…
baseline-ui
Quickly deslop UI code by fixing spacing, hierarchy, typography, and small layout issues. Use when the interface needs a fast cleanup or polish pass.