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.
npx agentmods add rules/cmnemoi/cursor-rules/3-scss-sass-1git clone --depth 1 https://github.com/cmnemoi/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/cmnemoi/cursor-rules/3-scss-sass-1)<a href="https://agentmods.dev/rules/cmnemoi/cursor-rules/3-scss-sass-1"><img src="https://agentmods.dev/badge/rules/cmnemoi/cursor-rules/3-scss-sass-1.svg" alt="Measured on agentmods" 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.00472 |
| Opus 5 | $0.00000 | $0.00236 |
| Sonnet 5 | $0.00000 | $0.00094 |
| Haiku 4.5 | $0.00000 | $0.00047 |
Grade A, and why
3-scss-sass@1 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 5d 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
File Organization:
- Use partial files prefixed with underscore (
_filename.scss) - Maintain a single source of truth for variables
- Group related styles in dedicated files
- Import partials in logical order (variables → mixins → placeholders → components)
Variables:
- Use semantic naming for variables (
$primary-colornot$blue) - Define color palette variables in a single location
- Use variables for repeated values (breakpoints, spacing, colors)
- Namespace variables by purpose (
$font-heading,$spacing-large)
Nesting:
- Limit nesting to maximum 3 levels
- Use parent selector (
&) for modifiers and pseudo-classes only - Extract deeply nested selectors to new components
- Avoid selector duplication within the same file
Mixins and Functions:
- Create mixins for repeated style patterns
- Document mixins with clear comments
- Use parameters with sensible defaults
- Prefer mixins for multi-property styles, functions for calculations
Placeholders:
- Use
%placeholderfor styles shared across multiple selectors - Prefer
@extend %placeholderover duplicating code - Group related placeholders in dedicated sections
- Document placeholder purpose with comments
Media Queries:
- Use variables for breakpoint values
- Place media queries inside the selector they modify
- Group related media query rules together
- Use mobile-first approach (min-width over max-width)
Performance:
- Avoid deep nesting that creates long selectors
- Minimize use of
@extendto prevent CSS bloat - Use direct child selectors (
>) when possible - Avoid universal selectors (
*) in complex selectors
Vue Integration:
- Use
scopedattribute for component-specific styles - Use
:deep()selector for targeting child components - Organize styles in the same order as template elements
- Separate global styles from component styles
Comments and Documentation:
- Document complex selectors and calculations
- Use consistent comment style for sections
- Include purpose and usage for mixins and functions
- Add TODOs for temporary solutions
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.
- 5d ago First seen · 60 lines · 472 tokens per session scan A 8783381fff5b
3-scss-sass@1 is a cursor rule published in the GitHub repository cmnemoi/cursor-rules (2 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 472 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-31.
Other cursor rules, from other repositories
css-styling
CSS architecture, tokens, and styling rules for this Docusaurus site. Apply when creating or modifying components, styles, layouts, or any UI-facing code.
codex-premium-website-skills
Apply Codex Skills standards to frontend, website, motion, accessibility, QA, agent reasoning, and handoff work.
shadcn-tailwind-guide
本规范定义了使用 shadcn/ui 和 Tailwind CSS 开发新组件的标准流程和最佳实践。.
ui-components
USE WHEN: Building UI components, structuring layouts, and applying styles using Tailwind CSS.
performance
Frontend performance optimization rules. Apply when optimizing UI or bundle.
css-render-blocking-diagnosis
Cursor rule "css-render-blocking-diagnosis" from adobecom/da-express-milo, covering css render-blocking diagnosis & resolution, critical learning from 98 pagespeed achievement, primary diagnostic protocol, step 1: css blocking symptom recognition and step 2: css loading sequence audit.