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/private-collections)<a href="https://agentmods.dev/rules/seite-sh/seite/private-collections"><img src="https://agentmods.dev/badge/rules/seite-sh/seite/private-collections/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/private-collections"><img src="https://agentmods.dev/badge/rules/seite-sh/seite/private-collections.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.00680 |
| Opus 5.5 | $0.00000 | $0.00272 |
| Sonnet 5.5 | $0.00000 | $0.00136 |
| Haiku 4.5 | $0.00000 | $0.00068 |
Grade A, and why
private-collections 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Private collections and password access
A collection can set private = true in seite.toml to keep its content out of public discovery while still building its hub and pages:
[[collections]]
name = "docs"
private = true
url_prefix = "/docs"
default_template = "doc.html"
Its pages are excluded from the homepage listing, sitemap.xml, llms.txt, llms-full.txt, search-index.json, RSS/Atom feeds, and tag pages. Every page also gets noindex, nofollow unless it supplies its own robots frontmatter. Without [access], this remains discovery-only and does not authenticate requests.
Enable password access on Cloudflare Pages
Add the site-level access configuration:
[access]
mode = "password"
session_hours = 168
With [access] present, every private = true collection is password protected by the generated Cloudflare Pages Worker. A collection's url_prefix protects that path. An empty prefix protects the whole main domain. A private collection with subdomain protects its entire subdomain output.
Translated collection pages are protected under every configured language prefix. Password access owns the generated _worker.js and _routes.json; remove custom versions from public/ before enabling it.
Each private collection has a password group. It defaults to the collection name; set access_group explicitly to share a password or give paths separate passwords:
[[collections]]
name = "docs"
private = true
access_group = "staff"
url_prefix = "/docs"
Inspect and set groups with:
seite access groups
seite access set-password staff
seite deploy
The password is prompted securely and staged for production and preview on the relevant Cloudflare Pages project. It is never stored in the repository or passed as a command-line argument. Deploy from the Pages project's configured production branch to activate production; projects created by seite use main. Run seite deploy --preview to activate preview. Password access currently supports Cloudflare Pages only.
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 · 73 lines · 0 tokens per session scan A 09ff8cca20ae
private-collections 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 680 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.