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/agenthosttestinggit 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.00575 | $0.00575 |
| Opus 5 | $0.00287 | $0.00287 |
| Sonnet 5 | $0.00115 | $0.00115 |
| Haiku 4.5 | $0.00057 | $0.00057 |
Grade A, and why
agentHostTesting 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 — 39 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Host
The agent host communicates via the Agent Host Protocol. The specification for this lives in a directory ../agent-host-protocol as a sibling of the VS Code directory.
If this directory doesn't exist, you should use the "ask questions" tool to ask the user if they want to clone [email protected]:microsoft/agent-host-protocol.git to that directory. After doing so, you should also prompt the user to add file:///<path/to/agent-host-protocol>/plugins/copilot-plugin as a plugin in their chat.pluginLocations settings.
Overall Protocol
The sessions process is a portable, standalone server that multiple clients can connect to. Clients see a synchronized view of sessions and can send commands that are reflected back as state-changing actions. The protocol is designed around four requirements:
- Synchronized multi-client state — an immutable, redux-like state tree mutated exclusively by actions flowing through pure reducers. While there is the option to implement functionality via imperative commands, we ALWAYS prefer to model features as pure state and actions.
- Lazy loading — clients subscribe to state by URI and load data on demand. The session list is fetched imperatively. Large content (images, long tool outputs) is stored by reference and fetched separately.
- Write-ahead with reconciliation — clients optimistically apply their own actions locally, then reconcile when the server echoes them back alongside any concurrent actions from other clients or the server itself.
- Forward-compatible versioning — newer clients can connect to older servers. A single protocol version number maps to a capabilities object; clients check capabilities before using features.
See the agent host protocol documentation for more details.
Service Construction
Read src/vs/platform/agentHost/node/serviceBootstrapping.md before adding or
moving a node Agent Host service. It is the canonical guide for service
placement, static constructor arguments, activation, test overrides, and
disposal ownership.
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 · 39 lines · 575 tokens per session scan A d89031b9b5a2
agentHostTesting is an instructions file published in the GitHub repository microsoft/vscode (190,061 stars, last pushed yesterday), licensed MIT. It adds 575 tokens to every session, about $0.0029 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 copilot-instructions.md
Instructions for johnpapa/vscode-peacock, covering copilot instructions — peacock, project type, typescript conventions, vs code extension patterns and color handling.
page-agent AGENTS.md
Instructions for alibaba/page-agent, covering instructions for coding assistants, project overview, development commands, architecture and monorepo structure.
summarize AGENTS.md
Instructions for steipete/summarize, covering summarize guardrails and workspace layout (note).
vscode-peacock AGENTS.md
Instructions for johnpapa/vscode-peacock, covering peacock — agent guide, project overview, repository structure, tech stack and build & run.
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).
OneJS AGENTS.md
Instructions for Singtaa/OneJS, covering onejs v3: agent guide, requirements, install, project setup and build and live reload.