vscode-sidebar-terminal: Skill for Claude Code

.claude/skills/mcp-chrome-devtools/SKILL.md

mcp-chrome-devtools is a skill for Claude Code from s-hiraoku/vscode-sidebar-terminal. It costs 50 tokens per session (1,258 once invoked), scanned A, original, MIT.

A guide to using Chrome DevTools through an agent interface for inspecting and controlling web pages. Chrome DevTools is a browser tool for examining pages, errors, network traffic, and performance.

In plain words
What is it for?
Use it to debug websites, inspect requests and console errors, profile performance, automate browser actions, and capture page snapshots.
Why use it?
It gives a consistent process for selecting pages, inspecting their state, finding console or network problems, and testing interactions.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

This is s-hiraoku/vscode-sidebar-terminal's own configuration. It tells Claude Code how to work on vscode-sidebar-terminal itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything vscode-sidebar-terminal configures →

Reuse

Borrowing it

Nothing to install: this file belongs to s-hiraoku/vscode-sidebar-terminal. 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/s-hiraoku/vscode-sidebar-terminal/main/.claude/skills/mcp-chrome-devtools/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/s-hiraoku/vscode-sidebar-terminal

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.

agentmods badge for mcp-chrome-devtools

README.md
[![agentmods](https://agentmods.dev/badge/skills/s-hiraoku/vscode-sidebar-terminal/mcp-chrome-devtools/github.svg)](https://agentmods.dev/skills/s-hiraoku/vscode-sidebar-terminal/mcp-chrome-devtools)
Your own site
<a href="https://agentmods.dev/skills/s-hiraoku/vscode-sidebar-terminal/mcp-chrome-devtools"><img src="https://agentmods.dev/badge/skills/s-hiraoku/vscode-sidebar-terminal/mcp-chrome-devtools/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.

agentmods 80×15 button for mcp-chrome-devtools

Your own site · 80×15
<a href="https://agentmods.dev/skills/s-hiraoku/vscode-sidebar-terminal/mcp-chrome-devtools"><img src="https://agentmods.dev/badge/skills/s-hiraoku/vscode-sidebar-terminal/mcp-chrome-devtools.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 50 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,258 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. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 1 finding, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • medium Memory Poisoning · line 83
    Skill attempts to fill the context window with filler content, displacing legitimate instructions and safety constraints. This can degrade agent performance or bypass safety boundaries.
    Fix: Implement context-window management that detects and rejects padding or stuffing attempts. Prioritize system instructions over user-injected content.
How audits are shown
Origin original No closer match found 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00050 $0.01258
Opus 5 $0.00025 $0.00629
Sonnet 5 $0.00010 $0.00252
Haiku 4.5 $0.00005 $0.00126

Measured 9d ago against content hash 1dfeee5ba13b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

mcp-chrome-devtools 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 9d 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.

.claude/skills/mcp-chrome-devtools/SKILL.md · 199 lines

How it starts

The opening of the file, as written. The whole thing — 199 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Chrome DevTools MCP

Overview

This skill enables browser debugging and automation using Chrome DevTools through MCP. It provides access to Chrome DevTools features including page interaction, network analysis, console inspection, and performance tracing.

When to Use This Skill

  • Debugging web page issues
  • Analyzing network requests and responses
  • Inspecting console messages and errors
  • Performance profiling and tracing
  • Automated page interaction and testing
  • Taking screenshots and snapshots

Quick Start Workflow

  1. List pages: list_pages
  2. Select a page: select_page
  3. Take snapshot: take_snapshot
  4. Interact using uids from snapshot

Core Tools

Page Management

list_pages - Get all open pages

mcp__chrome-devtools__list_pages({})

select_page - Select a page for operations

mcp__chrome-devtools__select_page({ pageIdx: 0 })

new_page - Create a new page

mcp__chrome-devtools__new_page({ url: "https://example.com" })

close_page - Close a page

mcp__chrome-devtools__close_page({ pageIdx: 1 })

navigate_page - Navigate the selected page

mcp__chrome-devtools__navigate_page({ type: "url", url: "https://example.com" })
mcp__chrome-devtools__navigate_page({ type: "back" })
mcp__chrome-devtools__navigate_page({ type: "reload", ignoreCache: true })

Snapshots and Screenshots

take_snapshot - Get accessibility tree (preferred for interaction)

mcp__chrome-devtools__take_snapshot({})

take_screenshot - Capture visual screenshot

mcp__chrome-devtools__take_screenshot({
  format: "png",
  fullPage: true,
  filePath: "./screenshot.png"
})

Element Interaction

click - Click an element

mcp__chrome-devtools__click({ uid: "element-uid" })
mcp__chrome-devtools__click({ uid: "element-uid", dblClick: true })

fill - Fill input or select option

mcp__chrome-devtools__fill({ uid: "input-uid", value: "text" })

fill_form - Fill multiple form elements

mcp__chrome-devtools__fill_form({
  elements: [
    { uid: "username-uid", value: "user" },
    { uid: "password-uid", value: "pass" }
  ]
})

Read the full file on GitHub · 199 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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.

  1. 9d ago First seen · 199 lines · 50 tokens per session scan A 1dfeee5ba13b

Subscribe to this mod's changes

mcp-chrome-devtools is a skill published in the GitHub repository s-hiraoku/vscode-sidebar-terminal (21 stars, last pushed yesterday), licensed MIT. It adds 50 tokens to every session and 1,258 once invoked, about $0.0003 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-09-01.

Related

Other skills, from other repositories

chrome-devtools-cli

Use this skill to write shell scripts or run shell commands to automate tasks in the browser or otherwise use Chrome DevTools via CLI.

ChromeDevTools/chrome-devtools-mcp · 31 tokens

a11y-debugging

Uses Chrome DevTools MCP for accessibility (a11y) debugging and auditing based on web.dev guidelines. Use when testing semantic HTML, ARIA labels, focus states, keyboard navigation, tap targets, and color contrast.

ChromeDevTools/chrome-devtools-mcp · 50 tokens

chrome-devtools

Uses Chrome DevTools via MCP for efficient debugging, troubleshooting and browser automation. Use when debugging web pages, automating browser interactions, analyzing performance, or inspecting network requests. This skill does not apply to --slim mode (MCP configuration).

ChromeDevTools/chrome-devtools-mcp · 55 tokens

chrome-performance-optimizer

Autonomous multi-agent performance optimization loop for Chromium and V8. Supports profile-seeded mode (analyzing Speedometer 3 / JetStream profiles via pprof or Sagacity MCP) and pattern-driven discovery mode (fan-out exploration of Blink and V8 macro-patterns grounded in historical wins and past rejected CLs).…

chromium/chromium · 119 tokens

nullaway

Guide for resolving NullAway static analysis errors. Best practices for: Passing ObservableSupplier/Supplier Dereferencing potentially @Nullable values Adding @NullMarked to Java code.

chromium/chromium · 43 tokens

bisect

Bisect regressions or broken builds in the Chromium repository using deterministic binary search, checking out midpoint commits, syncing dependencies with gclient sync, compiling the target with autoninja, and querying the user for test results until the culprit commit is isolated.

chromium/chromium · 52 tokens