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/notebookgit 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.01105 | $0.01105 |
| Opus 5 | $0.00553 | $0.00553 |
| Sonnet 5 | $0.00221 | $0.00221 |
| Haiku 4.5 | $0.00111 | $0.00111 |
Grade A, and why
vscode notebook.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.
Copies of this mod
1 near-identical copy found in the catalogue:
- nyrve notebook.instructions.md — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Notebook Architecture
This document describes the internal architecture of VS Code's notebook implementation.
Model resolution
Notebook model resolution is handled by NotebookService. It resolves notebook models from the file system or other sources. The notebook model is a tree of cells, where each cell has a type (code or markdown) and a list of outputs.
Viewport rendering (virtualization)
The notebook viewport is virtualized to improve performance. Only visible cells are rendered, and cells outside the viewport are recycled. The viewport rendering is handled by NotebookCellList which extends WorkbenchList<CellViewModel>.
The rendering has the following steps:
- Render Viewport - Layout/render only the cells that are in the visible viewport
- Render Template - Each cell type has a template (code cell, markdown cell) that is instantiated via
CodeCellRendererorMarkupCellRenderer - Render Element - The cell content is rendered into the template
- Get Dynamic Height - Cell height is computed dynamically based on content (editor lines, outputs, etc.)
- Cell Parts Lifecycle - Each cell has lifecycle parts that manage focus, selection, and other state
Cell resize above viewport
When a cell above the viewport is resized (e.g., output grows), the viewport needs to be updated to maintain scroll position. This is handled by tracking scroll anchors.
Cell Rendering
The notebook editor renders cells through a contribution system. Cell parts are organized into two categories via CellPartsCollection:
- CellContentPart - Non-floating elements rendered inside a cell synchronously to avoid flickering
prepareRenderCell()- Prepare model (no DOM operations)renderCell()/didRenderCell()- Update DOM for the cellunrenderCell()- Cleanup when cell leaves viewportupdateInternalLayoutNow()- Update layout per cell layout changesupdateState()- Update per cell state changeupdateForExecutionState()- Update per execution state change
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 · 109 lines · 1,105 tokens per session scan A f8f6b89cd062
vscode notebook.instructions.md is an instructions file published in the GitHub repository microsoft/vscode (190,061 stars, last pushed yesterday), licensed MIT. It adds 1,105 tokens to every session, about $0.0055 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.