Borrowing it
Nothing to install: this file belongs to malwarebo/nyrve. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/malwarebo/nyrve/main/.github/instructions/interactive.instructions.mdgit clone --depth 1 https://github.com/malwarebo/nyrveWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/instructions/malwarebo/nyrve/interactive)<a href="https://agentmods.dev/instructions/malwarebo/nyrve/interactive"><img src="https://agentmods.dev/badge/instructions/malwarebo/nyrve/interactive/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/malwarebo/nyrve/interactive"><img src="https://agentmods.dev/badge/instructions/malwarebo/nyrve/interactive.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00938 | $0.00938 |
| Opus 5.5 | $0.00375 | $0.00375 |
| Sonnet 5.5 | $0.00188 | $0.00188 |
| Haiku 4.5 | $0.00094 | $0.00094 |
Grade A, and why
nyrve interactive.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 1mo 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.
This is a copy
100% identical to vscode interactive.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.
How it starts
The opening of the file, as written. The whole thing — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Interactive Window
The interactive window component enables extensions to offer REPL like experience to its users. VS Code provides the user interface and extensions provide the execution environment, code completions, execution results rendering and so on.
The interactive window consists of notebook editor at the top and regular monaco editor at the bottom of the viewport. Extensions can extend the interactive window by leveraging the notebook editor API and text editor/document APIs:
- Extensions register notebook controllers for the notebook document in the interactive window through
vscode.notebooks.createNotebookController. The notebook document has a special notebook view typeinteractive, which is contributed by the core instead of extensions. The registered notebook controller is responsible for execution. - Extensions register auto complete provider for the bottom text editor through
vscode.languages.registerCompletionItemProvider. The resource scheme for the text editor isinteractive-inputand the language used in the editor is determined by the notebook controller contributed by extensions.
Users can type in code in the text editor and after users pressing Shift+Enter, we will insert a new code cell into the notebook document with the content from the text editor. Then we will request execution for the newly inserted cell. The notebook controller will handle the execution just like it's in a normal notebook editor.
Interactive Window Registration
Registering a new editor type in the workbench consists of two steps:
- Register an editor input factory which is responsible for resolving resources with given
globpatterns. Here we register anInteractiveEditorInputfor all resources withvscode-interactivescheme. - Register an editor pane factory for the given editor input type. Here we register
InteractiveEditorfor our own editor inputInteractiveEditorInput.
The workbench editor service is not aware of how models are resolved in EditorInput, neither how EditorPanes are rendered. It only cares about the common states and events on EditorInput or EditorPane, i.e., display name, capabilities (editable), content change, dirty state change. It's EditorInput/EditorPane's responsibility to provide the right info and updates to the editor service. One major difference between Interactive Editor and other editor panes is Interactive Window is never dirty so users never see a dot on the editor title bar.
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.
- 1mo ago First seen · 51 lines · 938 tokens per session scan A 26ddeb782fd4
nyrve interactive.instructions.md is an instructions file published in the GitHub repository malwarebo/nyrve (5 stars, last pushed 4mo ago), licensed MIT. It adds 938 tokens to every session, about $0.0038 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to vscode interactive.instructions.md, differing in 0 lines, and is treated as a copy.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.