landing-write

landing-write is a command for Claude Code from seite-sh/seite. It costs 0 tokens per session (2,664 once invoked), scanned A, a copy of landing-write, MIT.

A command for writing landing pages, which are focused pages designed to guide visitors toward an action such as starting a trial, booking a demo, or becoming a lead.

In plain words
What is it for?
Use it to create SEO or PPC landing-page copy for a trial, demo, or lead goal from a topic or research brief.
Why use it?
It adapts the page for unpaid search traffic or paid advertising and keeps the writing focused on a chosen outcome.

Command for Claude Code

Install

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.

agentmods
npx agentmods add commands/seite-sh/seite/landing-write
Clone the repo
git clone --depth 1 https://github.com/seite-sh/seite

Made for: Claude Code.

Wrote 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.

agentmods badge for landing-write

README.md
[![agentmods](https://agentmods.dev/badge/commands/seite-sh/seite/landing-write.svg)](https://agentmods.dev/commands/seite-sh/seite/landing-write)
Your own site
<a href="https://agentmods.dev/commands/seite-sh/seite/landing-write"><img src="https://agentmods.dev/badge/commands/seite-sh/seite/landing-write.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,664 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.02664
Opus 5 $0.00000 $0.01332
Sonnet 5 $0.00000 $0.00533
Haiku 4.5 $0.00000 $0.00266

Measured 4d ago against content hash 545874d74dad, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

landing-write 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.

Origin

This is a copy

100% identical to landing-write — 0 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.

seite-sh/.claude/commands/landing-write.md · 427 lines

How it starts

The opening of the file, as written. The whole thing — 427 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Landing Page Write Command

Use this command to create high-converting landing pages optimized for either organic SEO traffic or paid PPC traffic.

Usage

/landing-write [topic or research brief] --type [seo|ppc] --goal [trial|demo|lead]

Examples:

  • /landing-write "product hosting for beginners" --type seo --goal trial
  • /landing-write "research/landing-brief-private-producting.md" --type ppc --goal demo
  • /landing-write "product monetization guide" --type seo --goal lead

Defaults:

  • --type seo (if not specified)
  • --goal trial (if not specified)

What This Command Does

  1. Creates conversion-optimized landing pages (not blog articles)
  2. Tailors content length and structure to page type (SEO vs PPC)
  3. Optimizes CTAs for the specified conversion goal
  4. Includes all CRO best practices (trust signals, risk reversal, etc.)
  5. Scores the page against landing page best practices

Pre-Writing Review

Required Context:

  • Landing Page Templates: @context/landing-page-templates.md for structure
  • CRO Best Practices: @context/cro-best-practices.md for conversion guidelines
  • Brand Voice: @context/brand-voice.md for tone and messaging

If Research Brief Available:

  • Review competitor analysis
  • Use recommended headlines
  • Reference identified pain points
  • Integrate suggested trust signals

SEO Landing Page Structure (--type seo)

Word Count: 1500-2500 words CTAs: 3-5 distributed throughout Internal Links: 2-3 strategic links

Content Structure

# [Benefit-Focused Headline with Keyword]

**Meta Title**: [50-60 chars, keyword + benefit]
**Meta Description**: [150-160 chars, includes CTA]
**Target Keyword**: [primary keyword]
**Page Type**: seo
**Conversion Goal**: [trial|demo|lead]

---

[HOOK: 2-3 sentences. Start with pain point, surprising stat, or question]

[Trust signal: "Join 50,000+ customers" or customer results]

**[Primary CTA Button →]**

## [H2: Problem/Pain Point Section]

[2-3 paragraphs acknowledging the reader's struggle]

[Mini-story with specific person and outcome]

## [H2: Solution Overview]

[Introduce how [YOUR COMPANY] solves this problem]

**Key Benefits:**
- **[Benefit 1]** - [One sentence]
- **[Benefit 2]** - [One sentence]
- **[Benefit 3]** - [One sentence]

**[Secondary CTA →]**

## [H2: Features That Deliver]

[3-5 features, each tied to a benefit]

### [Feature 1]
[2-3 sentences: what it is, why it matters]

### [Feature 2]
[Continue...]

## [H2: Social Proof]

"[Testimonial with specific results]"
— **[Name], [Product/Company]**

"[Second testimonial]"
— **[Name], [Product/Company]**

**Results our customers see:**
- [Specific result with number]
- [Specific result with number]

**[CTA Button →]**

## [H2: How It Works]

1. **[Step 1]** - [Brief description]
2. **[Step 2]** - [Brief description]
3. **[Step 3]** - [Brief description]

## [H2: FAQ Section]

**[Question addressing objection]?**
[Answer - 2-3 sentences]

**[Question addressing objection]?**
[Answer - 2-3 sentences]

[4-6 FAQs total]

## [H2: Ready to [Achieve Outcome]?]

[1-2 sentences summarizing the value]

**[Strong CTA Button →]**

[Risk reversal: "Free trial • No credit card • Cancel anytime"]

Read the full file on GitHub · 427 lines

Changes

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.

  1. 4d ago First seen · 427 lines · 0 tokens per session scan A 545874d74dad

Subscribe to this mod's changes

landing-write is a command published in the GitHub repository seite-sh/seite (20 stars, last pushed 19d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,664 tokens. A static security scan graded it A with 0 findings. It is 100% identical to landing-write, differing in 0 lines, and is treated as a copy.