data-files

data-files is a cursor rule for Cursor from seite-sh/seite. It costs 0 tokens per session (400 once invoked), scanned A, original, MIT.

A way to store structured site data in YAML, JSON, or TOML files and make it available to page templates during a build.

In plain words
What is it for?
Use it to define menus, footer links, author lists, settings, and nested data that templates can read.
Why use it?
It keeps navigation, authors, settings, and other reusable values separate from template code and page content.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

Good fit Use it to define menus, footer links, author lists, settings, and nested data that templates can read.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/seite-sh/seite/data-files
Install

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.

Clone the repo
git clone --depth 1 https://github.com/seite-sh/seite

Made for: Cursor.

Wrote 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.

agentmods badge for data-files

README.md
[![agentmods](https://agentmods.dev/badge/rules/seite-sh/seite/data-files/github.svg)](https://agentmods.dev/rules/seite-sh/seite/data-files)
Your own site
<a href="https://agentmods.dev/rules/seite-sh/seite/data-files"><img src="https://agentmods.dev/badge/rules/seite-sh/seite/data-files/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.

agentmods 80×15 button for data-files

Your own site · 80×15
<a href="https://agentmods.dev/rules/seite-sh/seite/data-files"><img src="https://agentmods.dev/badge/rules/seite-sh/seite/data-files.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 400 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00400
Opus 5.5 $0.00000 $0.00160
Sonnet 5.5 $0.00000 $0.00080
Haiku 4.5 $0.00000 $0.00040

Measured 17d ago against content hash 4736d0a621c1, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

data-files 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.

seite-sh/.cursor/rules/data-files.mdc · 54 lines

What it actually says

Data Files

The data/ directory holds structured data files (YAML, JSON, TOML) that are loaded at build time and injected into all template contexts as {{ data.filename }}.

How it works

  • data/nav.yaml → {{ data.nav }}
  • data/authors.json → {{ data.authors }}
  • data/settings.toml → {{ data.settings }}
  • Nested directories create nested keys: data/menus/main.yaml → {{ data.menus.main }}

Supported file types: .yaml / .yml, .json, .toml.

Theme integration

All 10 bundled themes conditionally render data.nav (navigation links) and data.footer (footer links + copyright). Example data/nav.yaml:

- title: Blog
  url: /posts
- title: About
  url: /about
- title: GitHub
  url: https://github.com/user/repo
  external: true

Example data/footer.yaml:

links:
  - title: GitHub
    url: https://github.com/user/repo
    external: true
copyright: "2026 My Company"

Internal links are auto-prefixed with {{ lang_prefix }} for i18n; external links (marked with external: true) get target="_blank".

Configuration

The data directory defaults to data/. Change it with data_dir = "my_data" under [build] in seite.toml.

Conflict detection

  • Two files with the same stem (authors.yaml + authors.json) → build error
  • A file and a directory with the same name → build error
Changes

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.

  1. 17d ago First seen · 54 lines · 0 tokens per session scan A 4736d0a621c1

Subscribe to this mod's changes

data-files 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 400 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.