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/rules/seite-sh/seite/seo-requirements)<a href="https://agentmods.dev/rules/seite-sh/seite/seo-requirements"><img src="https://agentmods.dev/badge/rules/seite-sh/seite/seo-requirements/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/rules/seite-sh/seite/seo-requirements"><img src="https://agentmods.dev/badge/rules/seite-sh/seite/seo-requirements.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.00921 |
| Opus 5.5 | $0.00000 | $0.00368 |
| Sonnet 5.5 | $0.00000 | $0.00184 |
| Haiku 4.5 | $0.00000 | $0.00092 |
Grade A, and why
seo-requirements 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 17d 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 — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SEO and GEO Requirements
These are non-negotiable rules for every page on this site. They apply when writing content, creating templates, or asking the AI agent to build or redesign anything.
Every page <head> MUST include
- Favicon —
<link rel="icon" href="/favicon.ico">(user placesfavicon.icoinpublic/) - Canonical URL —
<link rel="canonical" href="{{ site.base_url }}{{ page.url | default(value='/') }}">(deduplicates indexed URLs) - Open Graph tags —
og:type,og:url,og:title,og:description,og:site_name,og:localeog:type = articlewhenpage.collectionis set;websitefor the homepageog:imageonly whenpage.imageis set — must be an absolute URL. Use{% set _abs_image = page.image %}{% if not page.image is starting_with("http") %}{% set _abs_image = site.base_url ~ page.image %}{% endif %}then reference{{ _abs_image }}og:image:widthandog:image:height— include1200and630(standard social preview dimensions)article:published_time— emit whenpage.collectionandpage.dateare setarticle:modified_time— emit whenpage.collectionandpage.updatedare set
- Twitter Card tags —
twitter:card,twitter:title,twitter:description,twitter:imagetwitter:card = summary_large_imagewhenpage.imageis set;summaryotherwisetwitter:image— same absolutization asog:image(use_abs_imagevariable)
- JSON-LD structured data —
<script type="application/ld+json">block:BlogPostingfor posts (includedatePublished,dateModifiedifpage.updatedis set)Articlefor docs and other collection pagesWebSitefor the homepage/indexBreadcrumbListfor all collection pages (Home → Collection → Page)
- Markdown alternate link —
<link rel="alternate" type="text/markdown" title="Markdown" href="{{ site.base_url }}{{ page.url }}.md">(LLM-native differentiator — must includetitleattribute) - llms.txt discovery —
<link rel="alternate" type="text/plain" title="LLM Summary" href="/llms.txt"> - RSS autodiscovery —
<link rel="alternate" type="application/rss+xml" ...> - Language attribute —
<html lang="{{ lang }}">(already in bundled themes)
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.
- 17d ago First seen · 48 lines · 0 tokens per session scan A 41ce1f793dfe
seo-requirements is a cursor rule published in the GitHub repository seite-sh/seite (25 stars, last pushed 6d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 921 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-09-29.
Other cursor rules, from other repositories
frontend-architecture
Cursor rule "frontend-architecture" from tomasz-tomczyk/crit, covering frontend architecture, two-paradigm page fork, module pattern, shared modules (used by both modes) and code-review modules (used only by code-review mode).
proxy-auth-transport
Every CLI command or browser UI action that calls a crit-web API must work in both modes.
frontend-js
Cursor rule "frontend-js" from tomasz-tomczyk/crit, covering frontend js rules (semantic — eslint handles syntax/style), dom & events, state management, persisted settings (cookies, not localstorage) and error handling.
go
Cursor rule "go" from tomasz-tomczyk/crit, covering go code rules (semantic — linters handle syntax/style), struct & state integrity, code organization, git operations and daemon/server.
frontend-css
Cursor rule "frontend-css" from tomasz-tomczyk/crit, covering css rules, responsive & touch and selectors.
workflow
BDD-style workflow, UI screenshots in the PR, HTTP OpenAPI, config schema and CLI packaging sync before lint, final checks, the comment on an issue a merge closes and the cleanup after the merge.