vscode best-practices.instructions.md

Guidelines for using VS Code’s existing buttons, actions, toolbars, separators, and editor-session patterns when building interface features.

In plain words
What is it for?
Use it when adding buttons, menus, toolbars, editor actions, or other reusable interface controls.
Why use it?
It prevents each feature from inventing its own controls and helps new interface code behave consistently with the rest of VS Code.

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

Made for: GitHub Copilot.

Per session 1,188 This file is loaded in full into every session.
When invoked 1,188 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.01188 $0.01188
Opus 5 $0.00594 $0.00594
Sonnet 5 $0.00238 $0.00238
Haiku 4.5 $0.00119 $0.00119

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

Security

Grade A, and why

vscode best-practices.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 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.

.github/instructions/best-practices.instructions.md · 49 lines

How it starts

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

Best Practices

Buttons & Actions

  • Don't create a new class or custom CSS to render a button or action. Reuse the existing Button class (vs/base/browser/ui/button/button.ts) and the existing Action types (vs/base/common/actions.ts). This keeps theming, accessibility, and behavior consistent.
  • Render actions inside a toolbar rather than by hand. Prefer MenuWorkbenchToolBar (vs/platform/actions/browser/toolbar.ts): give it a MenuId so actions can be contributed from anywhere (contributions, other components) without coupling.
  • Use WorkbenchToolBar when you need explicit control over which actions render and where separators go.
  • Never add a separator while rendering an action. Add separators with the existing Separator class (vs/base/common/actions.ts).
  • If a MenuWorkbenchToolBar lives in a widget/view that can be rendered multiple times at once, give the toolbar a scoped IContextKeyService which is scoped to the dom element of that widget/view and set the context keys per individual widget/view instance.

Editor/Session Actions

  • Don't assume the action runs on the active editor/session. An action (e.g. one contributed to some editor or session related toolbar) can be triggered for an editor/session that isn't active. The run method receives arguments describing the invocation context (such as the originating editor group or the originating session).
  • Resolve editor action arguments with resolveCommandsContext (vs/workbench/browser/parts/editor/editorCommandsContext.ts) to get the correct editor(s) instead of reading editorService.activeEditor.
  • Support multi-selection. The resolved editor actions context can contain several editors (e.g. multi-selected tabs).

Context Keys

  • Don't use context keys as a source of truth for application logic (for example, by reading IContextKeyService.getContextKeyValue() and branching on the result). Read the state from its owning service or model instead. Context keys are intended for declarative enablement and visibility, such as when clauses, command preconditions, and menu contributions.

Read the full file on GitHub · 49 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. yesterday First seen · 49 lines · 1,188 tokens per session scan A 1f4558907bf6

Subscribe to this mod's changes

vscode best-practices.instructions.md is an instructions file published in the GitHub repository microsoft/vscode (190,061 stars, last pushed yesterday), licensed MIT. It adds 1,188 tokens to every session, about $0.0059 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.