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/Consensys/doc.lineaWrote 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/consensys/doc.linea/css-styling)<a href="https://agentmods.dev/rules/consensys/doc.linea/css-styling"><img src="https://agentmods.dev/badge/rules/consensys/doc.linea/css-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/consensys/doc.linea/css-styling"><img src="https://agentmods.dev/badge/rules/consensys/doc.linea/css-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.00000 | $0.01408 |
| Opus 5.5 | $0.00000 | $0.00563 |
| Sonnet 5.5 | $0.00000 | $0.00282 |
| Haiku 4.5 | $0.00000 | $0.00141 |
Grade A, and why
css-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 1mo 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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CSS and styling rules
This is a Docusaurus v3 site using Infima. The CSS is split into layers. Follow these rules for every UI change.
File structure
src/css/
custom.css ← Entry point (imports only, never add rules here)
tokens.css ← Design tokens, theme variables
fonts.css ← @font-face declarations
base.css ← Element resets (body, headings, tables)
utilities.css ← Utility classes used from MDX (.video-container, .img-*)
docusaurus-overrides.css ← Navbar, sidebar, TOC, breadcrumbs, admonitions, code blocks
vendor-overrides.css ← Algolia DocSearch overrides
Component styles live in co-located CSS Modules (styles.module.css).
Where to put new styles
| What you're styling | Where it goes |
|---|---|
| A React component | src/components/MyComponent/styles.module.css |
| A swizzled theme component | src/theme/ComponentName/styles.module.css |
| A new design token | src/css/tokens.css under :root or [data-theme] |
| A Docusaurus theme override (navbar, sidebar, TOC) | src/css/docusaurus-overrides.css |
| A global utility class used in MDX | src/css/utilities.css |
| A third-party plugin override | src/css/vendor-overrides.css |
Never add rules directly to custom.css. It is an import-only entry point.
Mandatory: use tokens, not hardcoded values
Brand colors (constant — use everywhere)
var(--linea-brand-navy) /* #190066 */
var(--linea-brand-purple) /* #6119ef */
var(--linea-brand-cyan) /* #61dfff */
var(--linea-brand-yellow) /* #fff068 */
var(--linea-purple-hover) /* #8e5dff */
Theme-aware tokens (switch automatically between light/dark)
var(--linea-text-primary) /* #121212 | #f8f7f2 */
var(--linea-text-secondary) /* #525252 | #d1d1d1 */
var(--linea-text-muted) /* #808080 | #808080 */
var(--linea-text-subtle) /* #a0a0a0 | #a0a0a0 */
var(--linea-border) /* #e5e5e5 | #333 */
var(--linea-border-subtle) /* #e5e5e5 | #2d2d2d */
var(--linea-surface-elevated)/* #efefeb | #2f2f2f */
var(--linea-hover-bg) /* #EFEFEB | rgba */
var(--linea-active-color) /* #6119ef | #a78bfa */
var(--linea-active-bg) /* rgba | rgba */
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.
- 1mo ago First seen · 140 lines · 0 tokens per session scan A b370832d01b6
css-styling is a cursor rule published in the GitHub repository Consensys/doc.linea (474 stars, last pushed 1mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,408 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-08-30.
Other cursor rules, from other repositories
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.
chakra-ui---accessibility-features
An accessibility rule for React interfaces built with Chakra UI, a component library. It covers semantic HTML, screen-reader labels, keyboard navigation, focus handling, and color contrast.
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.
chakra-ui---theme-directory-rules
Rules for organizing a Chakra UI theme into an entry file, foundational settings, and component-specific styles. The theme controls shared colors, fonts, spacing, breakpoints, and component variants.
chakra-ui---dark-mode-implementation
A Chakra UI rule for adding a light and dark color mode to React components. It covers switching modes, following the system preference, storing the choice, and preventing a flash of the wrong theme during loading.
documentation
Documentation discovery index for Lineth monorepo.