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/akseolabs-seo/cinematic-uiWrote 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/akseolabs-seo/cinematic-ui/cinematic-ui)<a href="https://agentmods.dev/rules/akseolabs-seo/cinematic-ui/cinematic-ui"><img src="https://agentmods.dev/badge/rules/akseolabs-seo/cinematic-ui/cinematic-ui/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/akseolabs-seo/cinematic-ui/cinematic-ui"><img src="https://agentmods.dev/badge/rules/akseolabs-seo/cinematic-ui/cinematic-ui.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.00049 | $0.00634 |
| Opus 5 | $0.00024 | $0.00317 |
| Sonnet 5 | $0.00010 | $0.00127 |
| Haiku 4.5 | $0.00005 | $0.00063 |
Grade A, and why
cinematic-ui 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 9d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- cinematic-ui — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cinematic Layout — Cursor Rule
Design the site like a film production, not like a generic landing page.
Core Principle
This is not a style picker. Do not select a visual theme from a menu. This is a reasoning workflow. You must research a real director and a specific film, extract cinematic grammar from that research, and translate it into page structure, composition, and motion.
The film is research input, not a spec sheet. The formal workflow begins when you turn those observations into artifacts.
Four-Phase Workflow (non-negotiable)
Phase 1: DECISIONS → Complete start questionnaire → decisions.md
Phase 2: STORYBOARD → Site-wide grammar → scene per page → signature composition → storyboard.md
Phase 3: SPEC → Extract CSS/JS from library entries → compiled-spec.md
Phase 4: BUILD → Implement from spec only → HTML / CSS / JS
Never skip phases. Never jump from user request to HTML without the artifacts.
Phase 2 Internal Order (non-negotiable)
- Site-wide cinematic grammar
- Per-page scene thesis
- Irreplaceable signature composition per page
- Shared system last
Start Questionnaire (run every invocation)
Ask:
- How to start: Screenshot / Step-by-step / Surprise me
- Image placeholders: Yes / No
- Site niche and page list
Key Rules
- Director + film must drive color, type, spacing, composition, and motion
- Every page needs one signature composition that cannot collapse into a generic default grid
fadeUp/opacity + translateYmax 2 times per page- At least 4 distinct entrance types per page
- Maximum 1 heavy interaction per page
- Grid is invisible alignment infrastructure — never the visible composition
- Do not expose director names, chapter labels, or workflow metadata in the final UI
Demo Uniqueness Protocol
When the same user has prior outputs in the workspace:
- Run a uniqueness audit before Phase 1
- Write a shell-ban list: traits that must not repeat
- Choose a different primary composition family from the most recent comparable output
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.
- 9d ago First seen · 71 lines · 49 tokens per session scan A 40c35b37149b
cinematic-ui is a cursor rule published in the GitHub repository akseolabs-seo/cinematic-ui (64 stars, last pushed 5mo ago), licensed MIT. It adds 49 tokens to every session and 634 once invoked, about $0.0002 per session on Opus 5. 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-08-30.
Other cursor rules, from other repositories
codex-premium-website-skills
Apply Codex Skills standards to frontend, website, motion, accessibility, QA, agent reasoning, and handoff work.
components
Component patterns and UI conventions.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.