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-audit)<a href="https://agentmods.dev/commands/seite-sh/seite/landing-audit"><img src="https://agentmods.dev/badge/commands/seite-sh/seite/landing-audit.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.1 | $0.00000 | $0.01931 |
| Opus 5 | $0.00000 | $0.00966 |
| Sonnet 5 | $0.00000 | $0.00386 |
| Haiku 4.5 | $0.00000 | $0.00193 |
Grade A, and why
landing-audit 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 8d 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-audit — 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 — 306 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Landing Page Audit Command
Use this command to audit existing landing pages for conversion optimization opportunities.
Usage
/landing-audit [URL or file path] --goal [trial|demo|lead]
Examples:
/landing-audit https://yoursite.com/private-producting-solutions//landing-audit landing-pages/product-hosting-beginners-2025-12-11.md --goal trial/landing-audit https://yoursite.com/pricing/ --goal trial
Defaults:
--goal trial(if not specified)
What This Command Does
- Fetches or reads the landing page content
- Runs comprehensive CRO analysis using multiple analyzers
- Pulls GA4 performance data (if available for [YOUR COMPANY] pages)
- Generates prioritized recommendations
- Saves audit report for reference
Analysis Modules Used
1. Landing Page Scorer
Module: data_sources/modules/landing_page_scorer.py
- Overall score (0-100) against CRO best practices
- Category scores: Above-fold, CTAs, Trust signals, Structure, SEO
- Critical issues and warnings
- Publishing readiness assessment
2. Above-the-Fold Analyzer
Module: data_sources/modules/above_fold_analyzer.py
- Headline quality assessment
- Value proposition clarity
- CTA visibility check
- Trust signal presence
- 5-second test evaluation
3. CTA Analyzer
Module: data_sources/modules/cta_analyzer.py
- CTA count and distribution
- Individual CTA quality scoring
- Goal alignment check
- Placement recommendations
4. Trust Signal Analyzer
Module: data_sources/modules/trust_signal_analyzer.py
- Testimonial analysis (count, quality, specificity)
- Social proof detection
- Risk reversal presence
- Authority signals
5. CRO Checker
Module: data_sources/modules/cro_checker.py
- Checklist-based audit (30+ checks)
- Pass/fail for each CRO best practice
- Critical failures identification
- Category-by-category breakdown
Process
Step 1: Content Retrieval
For URLs:
- Fetch page content using WebFetch tool
- Extract main content from HTML
- Convert to markdown for analysis
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.
- 8d ago First seen · 306 lines · 0 tokens per session scan A 90b0ade20730
landing-audit is a command published in the GitHub repository seite-sh/seite (20 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,931 tokens. A static security scan graded it A with 0 findings. It is 100% identical to landing-audit, 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.
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.
help
Get help with the hookify plugin.