A quality-testing agent for demonstrating changes in Visual Studio Code, a code editor. It investigates a pull request, exercises the affected user interface, and records the workflows as visual evidence.

Use it to inspect a VS Code pull request, find related documentation, automate the changed interface, test relevant workflows, and capture a demonstration.

It helps verify that a code change works through realistic editor interactions and creates material that can be attached to the pull request.

How malwarebo/nyrve configures Claude Code

Reuse

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.

Copy the file

curl -O https://raw.githubusercontent.com/malwarebo/nyrve/main/.github/agents/demonstrate.md

Clone the repo

git clone --depth 1 https://github.com/malwarebo/nyrve

Made for: Claude Code.

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

README.md

[![agentmods](https://agentmods.dev/badge/agents/malwarebo/nyrve/demonstrate/github.svg)](https://agentmods.dev/agents/malwarebo/nyrve/demonstrate)

Your own site

<a href="https://agentmods.dev/agents/malwarebo/nyrve/demonstrate"><img src="https://agentmods.dev/badge/agents/malwarebo/nyrve/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.

Your own site · 80×15

<a href="https://agentmods.dev/agents/malwarebo/nyrve/demonstrate"><img src="https://agentmods.dev/badge/agents/malwarebo/nyrve/demonstrate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 10 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,294 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

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

Measured 1mo ago against content hash 1b4254f87219, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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.

Origin

This is a copy

100% identical to Demonstrate — 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/agents/demonstrate.md · 131 lines

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-docs repository 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":true using the vscode_automation_settings_add_user_settings tool. This will ensure that Chat works without requiring sign-in.

Testing Phase

Use browser_snapshot to 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
search_pull_requests - Search PRs with filters (author, state, etc.)

Read the full file on GitHub · 131 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.

1mo ago First seen · 131 lines · 10 tokens per session scan A 1b4254f87219

Subscribe to this mod's changes

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

Browser automation Claude Code E2E testing Testing ai-agents ide

browser-tester-v2

Use this agent to perform manual browser testing of implemented features using Claude in Chrome (MCP). Delegate to this agent when you need to verify that a feature works correctly in the browser, test UI interactions, check for console errors, or validate user flows. Provide context about what was implemented and…

lipas-liikuntapaikat/lipas · 69 tokens

nyrve: Agent for Claude Code