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.
git 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-research)<a href="https://agentmods.dev/commands/seite-sh/seite/landing-research"><img src="https://agentmods.dev/badge/commands/seite-sh/seite/landing-research/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/commands/seite-sh/seite/landing-research"><img src="https://agentmods.dev/badge/commands/seite-sh/seite/landing-research.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.00000 | $0.01976 |
| Opus 5 | $0.00000 | $0.00988 |
| Sonnet 5 | $0.00000 | $0.00395 |
| Haiku 4.5 | $0.00000 | $0.00198 |
Grade A, and why
landing-research 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 9d 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-research — 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 — 337 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Landing Page Research Command
Use this command to research a landing page opportunity before creating it. Analyzes competitors, keywords, and provides strategic recommendations.
Usage
/landing-research [topic or keyword] --type [seo|ppc]
Examples:
/landing-research "product hosting for beginners" --type seo/landing-research "product free trial" --type ppc/landing-research "private producting solutions"
Defaults:
--type seo(if not specified)
What This Command Does
- Researches the target keyword and search intent
- Analyzes top competitor landing pages (5-10)
- Identifies gaps and opportunities
- Recommends headlines, CTAs, and trust signals
- Creates a research brief for
/landing-write
Research Process
Step 1: Keyword & Intent Analysis
For SEO Pages:
- Analyze search volume and difficulty (via DataForSEO if available)
- Classify search intent (informational, commercial, transactional)
- Identify related keywords and questions
- Check SERP features (featured snippets, PAA, ads)
For PPC Pages:
- Focus on commercial/transactional intent
- Identify ad copy patterns from competitors
- Note CPC and competition level
- Analyze landing page message match requirements
Step 2: Competitor Analysis
Analyze top 5-10 competitors for the keyword:
Content Analysis:
- Page length (word count)
- Structure (sections, H2s)
- Content focus (features vs benefits)
CRO Elements:
- Headline patterns (what works)
- CTA copy and placement
- Trust signals used
- Risk reversal approaches
- Unique value propositions
Gaps to Exploit:
- What are competitors NOT saying?
- What objections are unaddressed?
- What social proof is missing?
- Where is messaging weak?
Step 3: Strategic Recommendations
Based on research, recommend:
Positioning:
- Primary angle to differentiate
- Key benefit to emphasize
- Target audience segment
Headlines:
- 5+ headline options based on competitor analysis
- Headline formulas that work in this space
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.
- 9d ago First seen · 337 lines · 0 tokens per session scan A eb501a2d708f
landing-research is a command published in the GitHub repository seite-sh/seite (20 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,976 tokens. A static security scan graded it A with 0 findings. It is 100% identical to landing-research, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.
doctor
Run TokenJam's health check — config, ingest endpoint, and storage. Equivalent to running tj doctor.
install
This page explains how the livewiki install CLI command detects installed coding agents and safely configures the livewiki MCP server entry, hook templates, shared skills, and optional pointer files.
pointer
This page documents the livewiki pointer subcommand, which manages an opt-in "pointer" block inside an AGENTS.md or CLAUDE.md file at the repository root.
index-cmd
The index command reindexes a repository and synchronizes its anchor ledger while selecting human-readable, JSON, or quiet output.
modernize-transform
Transform one legacy module to the target stack — idiomatic rewrite with behavior-equivalence tests.