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/cedricfressin/cursor.rulesWrote 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/cedricfressin/cursor.rules/006-ui-styling)<a href="https://agentmods.dev/rules/cedricfressin/cursor.rules/006-ui-styling"><img src="https://agentmods.dev/badge/rules/cedricfressin/cursor.rules/006-ui-styling/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/cedricfressin/cursor.rules/006-ui-styling"><img src="https://agentmods.dev/badge/rules/cedricfressin/cursor.rules/006-ui-styling.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.01191 | $0.01191 |
| Opus 5.5 | $0.00476 | $0.00476 |
| Sonnet 5.5 | $0.00238 | $0.00238 |
| Haiku 4.5 | $0.00119 | $0.00119 |
Grade A, and why
006-ui-styling 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 2mo 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 2mo ago First seen · 207 lines · 1,191 tokens per session scan A e9099fb0e747
006-ui-styling is a cursor rule published in the GitHub repository cedricfressin/cursor.rules (9 stars, last pushed 1y ago), with no licence file. It adds 1,191 tokens to every session, about $0.0048 per session on Opus 5.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-31.
Other cursor rules, from other repositories
compress-md-landing-page-prompt.crux
⟦CRUX:compress-md-landing-page-prompt.md Ρ{compress.md landing page} target=single static page for CRUX-Compress repo=github.com/zotoio/CRUX-Compress domain=compress.md; status=EXPERIMENTAL! msg="Reclaim ≤80% ctx window. CRUX→semantic core extraction" journey{land→compression viz»scroll»explore»expand spec»install}.
18-responsiveness-constraints
Responsiveness, constraints, auto-layout sizing (FILL/HUG/FIXED), min/max dimensions, adaptive components. Use when building responsive screens, setting constraints, or making components adapt to different screen sizes.
12-micro-interactions
Micro-interactions, hover effects, press feedback, scroll animations, prototype validation. Use when adding interactive details, prototyping flows, or polishing UI interactions.
chakra-ui-best-practices
A set of rules for building React interfaces with Chakra UI, a component library for styled and accessible user interfaces. It covers themes, responsive layouts, accessibility, performance, and reusable components.
nextjs-react-tailwind-cursorrules-prompt-file
Cursor rules for Next.js development with React and Tailwind CSS integration.
chakra-ui---responsive-design
Guidance for making Chakra UI layouts adapt to different screen sizes. It uses responsive style values, breakpoints, layout components, and conditional display rules for phones, tablets, and desktops.