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-publish)<a href="https://agentmods.dev/commands/seite-sh/seite/landing-publish"><img src="https://agentmods.dev/badge/commands/seite-sh/seite/landing-publish/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-publish"><img src="https://agentmods.dev/badge/commands/seite-sh/seite/landing-publish.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.01419 |
| Opus 5 | $0.00000 | $0.00709 |
| Sonnet 5 | $0.00000 | $0.00284 |
| Haiku 4.5 | $0.00000 | $0.00142 |
Grade A, and why
landing-publish 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 10d 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 — 217 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Landing Page Publish Command
Use this command to publish landing pages to the seite site as pages.
Usage
/landing-publish [file path] [options]
Options:
--noindex: Setrobots: noindexin frontmatter (for PPC pages)--draft: Keep as draft instead of publishing immediately
Examples:
/landing-publish content/pages/product-hosting-beginners.md/landing-publish content/pages/free-trial-ppc.md --noindex/landing-publish content/pages/pricing-comparison.md --draft
What This Command Does
- Validates the landing page file
- Checks landing page score (must be >=75)
- Verifies frontmatter format and required fields
- Runs
seite buildto verify it builds correctly - Optionally deploys with
seite deploy
Prerequisites
Before publishing, ensure:
- Landing page score is >=75 (run
/landing-auditfirst) - No critical issues remain
- All required frontmatter is present
- Content has been scrubbed for formatting artifacts
File Format Requirements
Landing page files must be in content/pages/ with proper seite frontmatter:
---
title: "Benefit-Focused Headline (50-60 chars)"
description: "Compelling meta description with primary keyword (150-160 chars)"
slug: page-slug
tags:
- landing-page
- target-keyword
image: /static/og-landing.png
extra:
page_type: seo
conversion_goal: trial
target_keyword: "primary keyword"
---
[Content...]
Publishing Process
Step 1: Validation
Check file exists in content/pages/ and contains required frontmatter:
title(required)description(required)slug(required)extra.target_keyword(required for SEO pages)extra.page_type(seo or ppc)extra.conversion_goal(trial, demo, or lead)
Step 2: Score Check
Run landing page scorer on the content:
- If score < 75, abort publishing
- Display current score and critical issues
- Suggest running
/landing-auditfor full analysis
Step 3: Frontmatter Adjustments
- Ensure
draft: trueis removed (or set tofalse) - If
--noindexflag is set, addrobots: noindexto frontmatter - Verify
descriptionis 150-160 characters - Verify
titleis 50-60 characters
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.
- 10d ago First seen · 217 lines · 0 tokens per session scan A c3c0cf4d6637
landing-publish is a command published in the GitHub repository seite-sh/seite (20 stars, last pushed 5d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,419 tokens. 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 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.