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 instructions/microsoft/vscode/best-practicesgit clone --depth 1 https://github.com/microsoft/vscodeWhat 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 | $0.01188 | $0.01188 |
| Opus 5 | $0.00594 | $0.00594 |
| Sonnet 5 | $0.00238 | $0.00238 |
| Haiku 4.5 | $0.00119 | $0.00119 |
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.
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
Buttonclass (vs/base/browser/ui/button/button.ts) and the existingActiontypes (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 aMenuIdso actions can be contributed from anywhere (contributions, other components) without coupling. - Use
WorkbenchToolBarwhen 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
Separatorclass (vs/base/common/actions.ts). - If a
MenuWorkbenchToolBarlives in a widget/view that can be rendered multiple times at once, give the toolbar a scopedIContextKeyServicewhich 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
runmethod 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 readingeditorService.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.
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.
- yesterday First seen · 49 lines · 1,188 tokens per session scan A 1f4558907bf6
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.
Other instructions, from other repositories
vscode-peacock AGENTS.md
Instructions for johnpapa/vscode-peacock, covering peacock — agent guide, project overview, repository structure, tech stack and build & run.
vscode-peacock copilot-instructions.md
Instructions for johnpapa/vscode-peacock, covering copilot instructions — peacock, project type, typescript conventions, vs code extension patterns and color handling.
code-by-wire CLAUDE.md
Instructions for luojiahai/code-by-wire, covering claude.md, development, website, architecture and code style.
swob AGENTS.md
Instructions for IvyYang1999/swob, covering swob 研发协作唯一规范, 不可越过的边界, 角色与职责, 生命周期 and 分支、worktree 与提交.
clodex-ide AGENTS.md
AGENTS.md instructions for mereyabdenbekuly-ctrl/clodex-ide, covering clodex repository agent rules, open/closed product boundary, commercial product invariant, current protocol v0 phase and current authorization state.
data-peek CLAUDE.md
Claude Code instructions for Rohithgilla12/data-peek, covering claude.md, project overview, commands, development (from root) and from apps/desktop.