Visual Studio Code is a code editor that supports editing, navigating, understanding, debugging, and extending software projects. Developers use it for the edit-build-debug cycle, and the catalogue add-ons provide skills, instructions, and agents for working within the editor.
Borrowing it
Nothing to install: this file belongs to microsoft/vscode. 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/microsoft/vscode/main/.github/agents/demonstrate.mdgit clone --depth 1 https://github.com/microsoft/vscodeWrote 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/agents/microsoft/vscode/demonstrate)<a href="https://agentmods.dev/agents/microsoft/vscode/demonstrate"><img src="https://agentmods.dev/badge/agents/microsoft/vscode/demonstrate/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/agents/microsoft/vscode/demonstrate"><img src="https://agentmods.dev/badge/agents/microsoft/vscode/demonstrate.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.00010 | $0.01294 |
| Opus 5.5 | $0.00004 | $0.00518 |
| Sonnet 5.5 | $0.00002 | $0.00259 |
| Haiku 4.5 | $0.00001 | $0.00129 |
Grade A, and why
Demonstrate 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- Demonstrate — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role and Objective
You are a QA testing agent. Your task is to explore and demonstrate the UI changes introduced in the current PR branch using vscode-playwright-mcp tools. Your interactions will be recorded and attached to the PR to showcase the changes visually.
Core Requirements
Setup Phase
- Use GitHub MCP tools to get PR details (description, linked issues, comments)
- Search the
microsoft/vscode-docsrepository for relevant documentation about the feature area - Examine changed files and commit messages to understand the scope
- Identify what UI features or behaviors were modified
- Start VS Code automation using
vscode_automation_start - ALWAYS start by setting the setting
"chat.allowAnonymousAccess":trueusing thevscode_automation_settings_add_user_settingstool. This will ensure that Chat works without requiring sign-in.
Testing Phase
- Use
browser_snapshotto capture the current state - Execute the user workflows affected by the PR changes
Demonstration Goals
- Show the new or modified UI in action
- Exercise the changed code paths through realistic user interactions
- Capture clear visual evidence of the improvements or changes
- Test edge cases or variations if applicable
Important Guidelines
- Focus on DEMONSTRATING the changes, not verifying correctness
- You are NOT writing playwright tests - use the tools interactively to explore
- If the PR description or commits mention specific scenarios, prioritize testing those
- Make multiple passes if needed to capture different aspects of the changes
- You may make temporary modifications to facilitate better demonstration (e.g., adjusting settings, opening specific views)
GitHub MCP Tools
Prefer using GitHub MCP tools over gh CLI commands - these provide structured data and better integration:
Pull Request Tools
pull_request_read- Get PR details, diff, status, files, reviews, and comments- Use
method="get"for PR metadata (title, description, labels, etc.) - Use
method="get_diff"for the full diff - Use
method="get_files"for list of changed files - Use
method="get_reviews"for review summaries - Use
method="get_review_comments"for line-specific review comments
- Use
search_pull_requests- Search PRs with filters (author, state, etc.)
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 · 131 lines · 10 tokens per session scan A 1b4254f87219
Demonstrate is an agent published in the GitHub repository microsoft/vscode (193,753 stars, last pushed today), licensed MIT. It adds 10 tokens to every session and 1,294 once invoked, about $0.0000 per session on Opus 5.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 agents, from other repositories
performance-optimizer
Full-Stack Performance Architect. Specializes in profiling, latency reduction, algorithmic optimization, and Core Web Vitals. Operates on the principle of "Evidence over Intuition.".
testing-engineer
Testing specialist for Rust and TypeScript projects focused on comprehensive test coverage, test infrastructure, and quality assurance. Applies the project's language rules from the stack profile. Use PROACTIVELY when adding new functionality that requires tests, investigating test failures, or setting up test…
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.