styles

A set of styling rules for a Visual Studio Code extension designed for Cursor, a code editor based on Visual Studio Code. It covers light and dark themes and encourages reuse of shared styles.

In plain words
What is it for?
Use it when building or maintaining Cursor extension webviews and their shared CSS files.
Why use it?
It helps keep extension screens consistent with Cursor's existing appearance and usable in both theme types. It also reduces duplicated styling rules.

Cursor rule for Cursor

Install

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.

agentmods
npx agentmods add rules/zackiles/cursor-workbench/styles
Clone the repo
git clone --depth 1 https://github.com/zackiles/cursor-workbench

Made for: Cursor.

Per session 115 This file is loaded in full into every session.
When invoked 115 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00115 $0.00115
Opus 5 $0.00057 $0.00057
Sonnet 5 $0.00023 $0.00023
Haiku 4.5 $0.00012 $0.00012

Measured yesterday against content hash 7ad70ffbccd6, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

styles 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 yesterday.

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.

.cursor/rules/local/styles.mdc · 9 lines

What it actually says

  • The is a vscode extension for desktop specifically designed for the vs code fork named Cursor, which shared the same general support for vs code extensions and configuration
  • The extensions webviews should work for both dark and light themes, relying on the default css classes that allow theme authors to overide styles
  • The extension should always leverage the base styles as much as possible in index.css and base.css
Changes

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.

  1. yesterday First seen · 9 lines · 115 tokens per session scan A 7ad70ffbccd6

Subscribe to this mod's changes

styles is a cursor rule published in the GitHub repository zackiles/cursor-workbench (3 stars, last pushed 11mo ago), licensed MIT. It adds 115 tokens to every session, about $0.0006 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-31.