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/i18n)<a href="https://agentmods.dev/rules/seite-sh/seite/i18n"><img src="https://agentmods.dev/badge/rules/seite-sh/seite/i18n/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/i18n"><img src="https://agentmods.dev/badge/rules/seite-sh/seite/i18n.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.00850 |
| Opus 5.5 | $0.00000 | $0.00340 |
| Sonnet 5.5 | $0.00000 | $0.00170 |
| Haiku 4.5 | $0.00000 | $0.00085 |
Grade A, and why
i18n 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Multi-language Support
Add translations by configuring languages in seite.toml and creating translated content files:
# seite.toml
[languages.es]
title = "Mi Sitio" # optional title override
description = "Un sitio web" # optional description override
Then create translated files with a language suffix before .md:
content/pages/about.md # English (default) → /about
content/pages/about.es.md # Spanish → /es/about
- Default language content lives at the root URL (
/about) - Other languages get a
/{lang}/prefix (/es/about) - Items with the same slug across languages are automatically linked as translations
- Per-language RSS feeds, sitemaps with hreflang alternates, and discovery files are generated automatically
- Without
[languages.*]config, the site is single-language and works as normal
i18n Template Helpers
Use {{ lang_prefix }} to prefix internal links for the current language (empty for default, "/es" for Spanish, etc.):
<a href="{{ lang_prefix }}/about">About</a>
In data/nav.yaml and data/footer.yaml, mark external links with external: true:
- title: Blog
url: /posts
- title: GitHub
url: https://github.com/user/repo
external: true
All bundled themes automatically apply lang_prefix to internal data file links and open external links in new tabs.
Translating UI Strings
All UI text in themes uses the {{ t.key }} object (search placeholder, pagination, 404 text, etc.). Override defaults by creating data/i18n/{lang}.yaml:
# data/i18n/es.yaml
search_placeholder: "Buscar…"
skip_to_content: "Ir al contenido principal"
no_results: "Sin resultados"
newer: "Más recientes"
older: "Más antiguos"
Available keys: search_placeholder, skip_to_content, no_results, newer, older, page_n_of_total, search_label, min_read, contents, tags, all_tags, tagged, changelog, roadmap, not_found_title, not_found_message, go_home, in_progress, planned, done, other, trust_center, trust_hero_subtitle, certifications_compliance, active, learn_more, auditor, scope, issued, expires, subprocessors, vendor, purpose, location, dpa, yes, no, faq.
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 · 89 lines · 0 tokens per session scan A ed44f6f95249
i18n 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 850 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.
docs-translation
The Russian documentation tree (docs/ru), what moves with an English page, the stamp, and the writing rules for Russian and English documentation.