agentmods.dev

vscode source-code-organization.instructions.md

Source-organization rules for VS Code, describing its code layers, runtime environments, dependency direction, and folder conventions. A layer is a group of code with defined responsibilities and allowed dependencies.

In plain words
What is it for?
Adding modules, services, or contributions; choosing between common, browser, Node.js, and Electron folders; and placing code in the correct VS Code layer.
Why use it?
They prevent modules from importing code they should not depend on, which keeps the large codebase easier to build, test, and maintain.

Instructions file for GitHub Copilot

190k yesterday A scan 662 tokens original MIT
View the source file microsoft/vscode
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/source-code-organization
Clone the repo
git clone --depth 1 https://github.com/microsoft/vscode

Made for: GitHub Copilot.

Per session 662 This file is loaded in full into every session.
When invoked 662 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.00662 $0.00662
Opus 5 $0.00331 $0.00331
Sonnet 5 $0.00132 $0.00132
Haiku 4.5 $0.00066 $0.00066

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

Security

Grade A, and why

vscode source-code-organization.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/source-code-organization.instructions.md · 70 lines

How it starts

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

Source Code Organization

Canonical reference: https://github.com/microsoft/vscode/wiki/Source-Code-Organization

Layers

The src/vs/ core is partitioned into ordered layers — each may only import from layers below it:

  1. base — General utilities and UI building blocks (no service dependencies)
  2. platform — Service injection support and base services shared across layers
  3. editor — Monaco Editor core (no node or electron-* dependencies)
  4. workbench — Full VS Code workbench, panels, views, and framework
  5. code — Desktop app entry point (Electron main, shared process, CLI)
  6. server — Server app entry point for remote development
  7. sessions — Agent Sessions window (may import from workbench and below; workbench must never import from sessions)

Target Environments

Within each layer, code is organized by runtime environment:

Folder APIs Available May Use
common Basic JavaScript only —
browser Web/DOM APIs common
node Node.js APIs common
electron-browser Browser + limited Electron IPC common, browser
electron-utility Electron utility process common, node
electron-main Electron main process common, node, electron-utility

Workbench Organization

  • vs/workbench/{common|browser|electron-browser} — minimal workbench core
  • vs/workbench/api — vscode.d.ts API provider
  • vs/workbench/services — core services (not contrib-specific)
  • vs/workbench/contrib — feature contributions

Contribution Rules

  • No dependency from outside contrib/ into contrib/
  • Each contribution has a single .contribution.ts entry point
  • Contributions expose internal API from a single common file
  • Cross-contribution dependencies use that common API — never reach into internals

Entry Points

Only code referenced from entry point files is loaded:

  • workbench.common.main.ts — shared dependencies
  • workbench.desktop.main.ts — desktop-only
  • workbench.web.main.ts — web-only

Read the full file on GitHub · 70 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 · 70 lines · 662 tokens per session scan A 20dfadeeeacb

Subscribe to this mod's changes

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

Browser automationLanguagesSecurityeditorelectronmicrosofttypescriptvisual-studio-code
Related

Other instructions, from other repositories

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.

johnpapa/vscode-peacock · 851 tokens

page-agent AGENTS.md

Instructions for alibaba/page-agent, covering instructions for coding assistants, project overview, development commands, architecture and monorepo structure.

alibaba/page-agent · 1,603 tokens

summarize AGENTS.md

Instructions for steipete/summarize, covering summarize guardrails and workspace layout (note).

steipete/summarize · 543 tokens

vscode-peacock AGENTS.md

Instructions for johnpapa/vscode-peacock, covering peacock — agent guide, project overview, repository structure, tech stack and build & run.

johnpapa/vscode-peacock · 1,938 tokens

vscode-angular-snippets AGENTS.md

Instructions for johnpapa/vscode-angular-snippets, covering angular snippets for vs code — agent guide, repository structure, tech stack, build & run and test in browser (vscode.dev mode).

johnpapa/vscode-angular-snippets · 1,584 tokens

OneJS AGENTS.md

Instructions for Singtaa/OneJS, covering onejs v3: agent guide, requirements, install, project setup and build and live reload.

Singtaa/OneJS · 3,400 tokens