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 agentmods add commands/seite-sh/seite/landing-writegit clone --depth 1 https://github.com/seite-sh/seiteWrote 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/seite-sh/seite/landing-write)<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>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 | $0.00000 | $0.02664 |
| Opus 5 | $0.00000 | $0.01332 |
| Sonnet 5 | $0.00000 | $0.00533 |
| Haiku 4.5 | $0.00000 | $0.00266 |
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.
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.
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
- Creates conversion-optimized landing pages (not blog articles)
- Tailors content length and structure to page type (SEO vs PPC)
- Optimizes CTAs for the specified conversion goal
- Includes all CRO best practices (trust signals, risk reversal, etc.)
- 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"]
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 First seen · 427 lines · 0 tokens per session scan A 545874d74dad
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.
Other commands, from other repositories
awesome-chatgpt
Search awesome-ChatGPT-repositories for open-source GitHub repositories related to ChatGPT and LLMs.
init
Scaffold a new MindBase project (v2 layout). Usage: /mb:init [template] [-- mission ...].
commit
智能生成 Git 提交信息并提交.
pr
Handle the full workflow from current branch state to an open, CI-monitored pull request.
doctor.es
Diagnostica problemas de inferencia LLM en Mac: asiai doctor verifica el estado de los motores, conflictos de puertos, carga de modelos y estado de la GPU.
claude-request
Send a prompt to Claude Code via the LLM gateway with session tracking.