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/templates)<a href="https://agentmods.dev/rules/seite-sh/seite/templates"><img src="https://agentmods.dev/badge/rules/seite-sh/seite/templates/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/templates"><img src="https://agentmods.dev/badge/rules/seite-sh/seite/templates.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.01611 |
| Opus 5.5 | $0.00000 | $0.00644 |
| Sonnet 5.5 | $0.00000 | $0.00322 |
| Haiku 4.5 | $0.00000 | $0.00161 |
Grade A, and why
templates 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Templates and Themes
Templates use Tera syntax (Jinja2-compatible). All templates extend base.html.
Available Themes
| Theme | Description |
|---|---|
default |
Clean, readable with system fonts |
minimal |
Typography-first, serif |
dark |
Dark mode (true black, violet accent) |
docs |
Sidebar layout for documentation |
brutalist |
Neo-brutalist: thick borders, hard shadows, yellow accent |
bento |
Card grid layout with rounded corners and soft shadows |
landing |
Marketing landing page with hero section |
terminal |
Monospace hacker aesthetic, green-on-black |
magazine |
Multi-column editorial layout |
academic |
Clean scholarly style with serif typography |
Apply with seite theme apply <name>. This overwrites templates/base.html.
Template Variables
Available in all templates:
| Variable | Type | Description |
|---|---|---|
site.title |
string | Site title (language-specific if multilingual) |
site.description |
string | Site description |
site.base_url |
string | Base URL (e.g., https://example.com) |
site.language |
string | Default language code (configured in seite.toml) |
site.author |
string | Author name |
lang |
string | Current page language code |
default_language |
string | Default language code (same as site.language) |
lang_prefix |
string | URL prefix for current language (empty for default, "/es" for Spanish, etc.) |
t |
object | UI translation strings (override via data/i18n/{lang}.yaml) |
translations |
array | Translation links [{lang, url}] (empty if no translations) |
data |
object | Data files — data/nav.yaml → {{ data.nav }} (see Data Files section) |
page.title |
string | Page title |
page.content |
string | Rendered HTML (use {{ page.content | safe }}) |
page.date |
string? | Publish date (if set) |
page.updated |
string? | Last-modified date (from updated: frontmatter) |
page.description |
string? | Page description |
page.image |
string? | Social-preview image URL (from image: frontmatter) |
page.tags |
array | Tags |
page.url |
string | URL path |
page.slug |
string | URL slug (e.g., hello-world) |
page.collection |
string | Collection name (e.g., posts) — empty string on homepage |
page.lang |
string | Language code for this page |
page.robots |
string? | Per-page robots directive (from robots: frontmatter) |
page.word_count |
number | Word count |
page.reading_time |
number | Estimated reading time in minutes (238 WPM) |
page.excerpt |
string? | Auto-extracted excerpt (from <!-- more --> marker or first paragraph) |
page.toc |
string | Auto-generated table of contents HTML from heading hierarchy |
page.extra |
object | Arbitrary data from extra: frontmatter — access via {{ page.extra.field }} |
nav |
array | Sidebar nav sections [{name, label, items: [{title, url, active}]}] |
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 · 122 lines · 0 tokens per session scan A dd06c5ece172
templates 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 1,611 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.
ui-assets
Docker staging for symlinked SPA and documentation assets.