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 skills/microsoft/vscode-copilot-chat/launchnpx skills add microsoft/vscode-copilot-chat --skill launchgit clone --depth 1 https://github.com/microsoft/vscode-copilot-chatWhat 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.00080 | $0.03548 |
| Opus 5 | $0.00040 | $0.01774 |
| Sonnet 5 | $0.00016 | $0.00710 |
| Haiku 4.5 | $0.00008 | $0.00355 |
Grade A, and why
launch 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.
How it starts
The opening of the file, as written. The whole thing — 336 lines — stays where its author put it; the contents beside it link to each section on GitHub.
VS Code Extension Automation
Automate VS Code Insiders with the Copilot Chat extension using agent-browser. VS Code is built on Electron/Chromium and exposes a Chrome DevTools Protocol (CDP) port that agent-browser can connect to, enabling the same snapshot-interact workflow used for web pages.
Prerequisites
agent-browsermust be installed. It's available in the project's devDependencies — runnpm install. Usenpx agent-browserif it's not on your PATH, or install globally withnpm install -g agent-browser.code-insidersis required. This extension uses 58 proposed VS Code APIs and targetsvscode ^1.110.0-20260223. VS Code Stable will not activate it — you must use VS Code Insiders.- The extension must be compiled first. Use
npm run compilefor a one-shot build, ornpm run watchfor iterative development. - CSS selectors are internal implementation details. Selectors like
.interactive-input-part,.monaco-editor, and.view-lineare VS Code internals that may change across versions. If automation breaks after a VS Code update, re-snapshot and check for selector changes.
Core Workflow
- Build the extension
- Launch VS Code Insiders with the extension and remote debugging enabled
- Connect agent-browser to the CDP port
- Snapshot to discover interactive elements
- Interact using element refs
- Re-snapshot after navigation or state changes
📸 Take screenshots for a paper trail. Use
agent-browser screenshot <path>at key moments — after launch, before/after interactions, and when something goes wrong. Screenshots provide visual proof of what the UI looked like and are invaluable for debugging failures or documenting what was accomplished.Save screenshots inside
.vscode-ext-debug/screenshots/(gitignored) using a timestamped subfolder so each run is isolated and nothing gets overwritten:# Create a timestamped folder for this run's screenshots SCREENSHOT_DIR=".vscode-ext-debug/screenshots/$(date +%Y-%m-%dT%H-%M-%S)" mkdir -p "$SCREENSHOT_DIR" # Windows (PowerShell): # $screenshotDir = ".vscode-ext-debug\screenshots\$(Get-Date -Format 'yyyy-MM-ddTHH-mm-ss')" # New-Item -ItemType Directory -Force -Path $screenshotDir # Save a screenshot (path is a positional argument — use ./ or absolute paths) # Bare filenames without ./ may be misinterpreted as CSS selectors agent-browser screenshot "$SCREENSHOT_DIR/after-launch.png"
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.
- 2d ago First seen · 336 lines · 80 tokens per session scan A bdc4e8378a88
launch is a skill published in the GitHub repository microsoft/vscode-copilot-chat (9,977 stars, last pushed 3mo ago), licensed MIT. It adds 80 tokens to every session and 3,548 once invoked, about $0.0004 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 skills, from other repositories
general-video
Author or edit a custom HyperFrames composition when no specialized workflow fits, or when BRIEF.md sets flow: companion. Use for longer or multi-scene pieces, brand and sizzle reels, montages, static loops, static title cards, footage remixes, and freeform builds. Use motion-graphics instead for a short unnarrated…
use-agent-browser-for-airi
Test AIRI display-model imports with agent-browser across stage-tamagotchi Electron, stage-web, and stage-pocket mobile web layouts. Use when uploading and verifying contributor-supplied Live2D ZIP, VRM, or MMD ZIP/PMX/PMD files through AIRI's model selector, including onboarding bypass, format-specific import…
opencli-sitemap-author
Use when creating or maintaining OpenCLI site sitemaps: agent-facing navigation, page-state, action, workflow, API-reference, pitfall, and fallback knowledge for a website. Use after browser exploration discovers durable site context, when a sitemap is stale, or when promoting local site knowledge into the repo.
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
pinchtab-mcp
Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.
mintlify-preview
Run the public Mintlify product docs site locally for live preview. Use when previewing or iterating on docs under docs/ (.mdx/.md pages, docs.json nav), or when the user says "start the docs", "run mintlify", "preview the docs site".