vscode design-tokens.instructions.md

Guidance for using named Visual Studio Code design-system tokens for sizes such as spacing, corner radii, font sizes, and icon sizes. Tokens are shared CSS variables that represent approved design values.

In plain words
What is it for?
Use it when writing or editing CSS that controls padding, margins, gaps, dimensions, rounding, typography, icons, or borders.
Why use it?
It keeps new CSS consistent with the existing interface and avoids hardcoded values that can fail style checks or drift from the design system.

Instructions file for GitHub Copilot

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 instructions/microsoft/vscode/design-tokens
Clone the repo
git clone --depth 1 https://github.com/microsoft/vscode

Made for: GitHub Copilot.

Per session 2,627 This file is loaded in full into every session.
When invoked 2,627 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.02627 $0.02627
Opus 5 $0.01314 $0.01314
Sonnet 5 $0.00525 $0.00525
Haiku 4.5 $0.00263 $0.00263

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

Security

Grade A, and why

vscode design-tokens.instructions.md 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.

.github/instructions/design-tokens.instructions.md · 193 lines

How it starts

The opening of the file, as written. The whole thing — 193 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Design tokens for sizing, spacing & radii

These tokens are the moves, not the reasoning. They implement the design philosophy (Values → Principles → Moves): reach for a token after naming the feeling and the principle it serves - a radius is an elevation tier, a font is a type role, not a number. See the design-philosophy skill for the full vocabulary, worked examples, and how to give UI feedback in design terms.

VS Code ships a design-system size ramp. These tokens are registered in baseSizes.ts and emitted as --vscode-* CSS variables. When generating or editing CSS, use the token variable instead of a raw px value wherever a token exists for that value. This keeps new UI visually consistent with the design system.

Every --vscode-* size var you reference must already exist in vscode-known-variables.json ("sizes" array, alphabetically sorted) or stylelint/hygiene fails. Adding a new token means adding it both in baseSizes.ts and that JSON file.

Spacing — padding, margin, gap

Use for padding, margin, gap, and fixed width/height of spacers. The numeric token name is the value in tenths of a px (size200 = 20px).

px Variable
0 --vscode-spacing-sizeNone
2 --vscode-spacing-size20
4 --vscode-spacing-size40
6 --vscode-spacing-size60
8 --vscode-spacing-size80
10 --vscode-spacing-size100
12 --vscode-spacing-size120
16 --vscode-spacing-size160
20 --vscode-spacing-size200
24 --vscode-spacing-size240
28 --vscode-spacing-size280
32 --vscode-spacing-size320
36 --vscode-spacing-size360
40 --vscode-spacing-size400
/* token   */          padding: var(--vscode-spacing-size80) var(--vscode-spacing-size120);
/* also ok */          padding: 8px 12px;   /* on-scale raw px is fine */
/* avoid   */          padding: 5px 7px;    /* off-scale - breaks rhythm */

Read the full file on GitHub · 193 lines

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. 2d ago First seen · 193 lines · 2,627 tokens per session scan A 7a61a02efbc0

Subscribe to this mod's changes

vscode design-tokens.instructions.md is an instructions file published in the GitHub repository microsoft/vscode (190,384 stars, last pushed today), licensed MIT. It adds 2,627 tokens to every session, about $0.0131 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-30.