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/Scopeo/draftnrunWrote 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/scopeo/draftnrun/back-office-styling)<a href="https://agentmods.dev/rules/scopeo/draftnrun/back-office-styling"><img src="https://agentmods.dev/badge/rules/scopeo/draftnrun/back-office-styling.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.00782 |
| Opus 5 | $0.00000 | $0.00391 |
| Sonnet 5 | $0.00000 | $0.00156 |
| Haiku 4.5 | $0.00000 | $0.00078 |
Grade A, and why
back-office-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 2d 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Back-office styling
Vuetify first
Use Vuetify components and their built-in props/classes for all UI.
Prefer Vuetify utility classes (pa-4, mt-2, text-primary, bg-surface) over custom CSS.
Only write custom SCSS when Vuetify doesn't cover the need.
Design tokens
Colors and Vuetify component defaults: src/plugins/vuetify/theme.ts and defaults.ts.
Spacing, layout dimensions, and occasional global Vuetify adjustments (card actions, pill-tab typography, etc.): src/assets/styles/variables/_tokens.scss.
Never hard-code color hex values in components — use theme tokens via:
- Vuetify props:
color="primary",color="error" - CSS variables:
rgb(var(--v-theme-primary)),rgb(var(--v-theme-surface)) - Utility classes:
text-primary,bg-surface
Color palette (light theme)
| Token | Value | Note |
|---|---|---|
| primary | #22577A |
Brand color — do not change |
| secondary | #38A3A5 |
|
| success | #2E7D32 |
|
| info | #1976D2 |
|
| warning | #F59E0B |
|
| error | #EF4444 |
|
| background | #FAF9F7 |
Warm off-white |
| surface | #FDFCFA |
Warm white |
Grey scale uses stone (warm) tones, not zinc (cool).
Design feel
The design follows a "calm technology" aesthetic inspired by Anthropic/Claude:
- Warm stone greys instead of cool zinc
- Subtle borders (
border-opacity: 0.05), minimal shadows - Outlined fields use softened borders (
--v-field-border-opacity: 0.18in_tokens.scss) to avoid heavy "black rectangle" outlines - Soft hover states (background tint, not border glow)
- Generous spacing and deliberate transitions (
0.2s ease-out) - Serif headings + sans-serif body for a literary, sophisticated feel
Fonts
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.
- 2d ago First seen · 75 lines · 0 tokens per session scan A 0aa2725170f9
back-office-styling is a cursor rule published in the GitHub repository Scopeo/draftnrun (30 stars, last pushed 4d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 782 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-04.
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
A guide to building new components with shadcn/ui and Tailwind CSS, a utility-based system for styling interfaces.
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.