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/shortcodes)<a href="https://agentmods.dev/rules/seite-sh/seite/shortcodes"><img src="https://agentmods.dev/badge/rules/seite-sh/seite/shortcodes/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/shortcodes"><img src="https://agentmods.dev/badge/rules/seite-sh/seite/shortcodes.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.00466 |
| Opus 5.5 | $0.00000 | $0.00186 |
| Sonnet 5.5 | $0.00000 | $0.00093 |
| Haiku 4.5 | $0.00000 | $0.00047 |
Grade A, and why
shortcodes 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.
What it actually says
Shortcodes
Shortcodes are reusable content components you can use inside markdown files.
Inline shortcodes (raw HTML output)
{{< youtube(id="dQw4w9WgXcQ") >}}
{{< vimeo(id="123456") >}}
{{< gist(user="octocat", id="abc123") >}}
{{< figure(src="/static/photo.jpg", caption="A great photo", alt="Description") >}}
Body shortcodes (markdown-processed body)
{{% callout(type="warning") %}}
This is **bold** markdown inside a callout box.
{{% end %}}
Callout types: info, warning, danger, tip
Built-in shortcodes
| Shortcode | Type | Parameters |
|---|---|---|
youtube |
inline | id (required), start, title |
vimeo |
inline | id (required), title |
gist |
inline | user (required), id (required) |
figure |
inline | src (required), alt, caption, width, height, class |
callout |
body | type (default: info) |
Custom shortcodes
Create Tera templates in templates/shortcodes/. Example templates/shortcodes/alert.html:
<div class="alert alert-{{ level }}">{{ body }}</div>
Use in markdown: {{% alert(level="error") %}}Something went wrong{{% end %}}
Shortcode templates have access to {{ page }} and {{ site }} context variables.
Syntax gotcha
Inline shortcodes self-close — {{< name(args) >}} — and body shortcodes end with a literal {{% end %}}. There is no Hugo-style {{< /name >}} closing tag; writing one fails the build with invalid shortcode syntax.
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 · 55 lines · 0 tokens per session scan A 4ab95ebf2f61
shortcodes 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 466 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.