nyrve notebook.instructions.md

Architecture guidance for VS Code's notebook and interactive coding components. A notebook combines code or text cells with their outputs, and the guide explains how those cells are loaded and displayed.

In plain words
What is it for?
Use it when changing or debugging code under VS Code's notebook component, including cell models, rendering, and visible-cell management.
Why use it?
It gives developers a map of the internal parts involved when notebook cells, outputs, focus, sizing, or scrolling behave incorrectly.

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/malwarebo/nyrve/notebook
Clone the repo
git clone --depth 1 https://github.com/malwarebo/nyrve

Made for: GitHub Copilot.

Per session 1,105 This file is loaded in full into every session.
When invoked 1,105 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin 100% copy Near-identical to another mod 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.01105 $0.01105
Opus 5 $0.00553 $0.00553
Sonnet 5 $0.00221 $0.00221
Haiku 4.5 $0.00111 $0.00111

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

Security

Grade A, and why

nyrve 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 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.

Origin

This is a copy

100% identical to vscode notebook.instructions.md — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.github/instructions/notebook.instructions.md · 109 lines

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>.

Viewport Rendering

The rendering has the following steps:

  1. Render Viewport - Layout/render only the cells that are in the visible viewport
  2. Render Template - Each cell type has a template (code cell, markdown cell) that is instantiated via CodeCellRenderer or MarkupCellRenderer
  3. Render Element - The cell content is rendered into the template
  4. Get Dynamic Height - Cell height is computed dynamically based on content (editor lines, outputs, etc.)
  5. 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 Resize Above Viewport

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 cell
    • unrenderCell() - Cleanup when cell leaves viewport
    • updateInternalLayoutNow() - Update layout per cell layout changes
    • updateState() - Update per cell state change
    • updateForExecutionState() - Update per execution state change

Read the full file on GitHub · 109 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 · 109 lines · 1,105 tokens per session scan A f8f6b89cd062

Subscribe to this mod's changes

nyrve notebook.instructions.md is an instructions file published in the GitHub repository malwarebo/nyrve (5 stars, last pushed 2mo ago), 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. It is 100% identical to vscode notebook.instructions.md, differing in 0 lines, and is treated as a copy.