agentmods.dev

cuecards: Skill for Claude Code

.agents/skills/vc-chrome-devtools/SKILL.md

vc:chrome-devtools is a skill for Claude Code from opencue/cuecards. It costs 38 tokens per session (5,688 once invoked), scanned A, a copy of ck:chrome-devtools, MIT.

A browser automation tool built around Puppeteer, a library for controlling Chrome with code. It can keep browser sessions open while you inspect and operate web pages.

In plain words
What is it for?
Use it to take screenshots, inspect performance and network activity, scrape pages, automate forms, review accessibility structure, and debug JavaScript in Chrome.
Why use it?
It removes the need to perform repetitive browser checks manually and helps investigate problems that only appear in a running page.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: installed under .agents/ (shared by several agents); mentions Codex.

This is opencue/cuecards's own configuration. It tells Claude Code how to work on cuecards 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 cuecards configures →

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is node "$SKILL_DIR/aria-snapshot.js" --url https://example.com --output ./.Codex/chrome-devtools/snapshots/page.yaml.

not rated 5repo today A scan 38 tokens copy · 91% MIT
View source ↗ opencue/cuecards opencue.github.io
Reuse

Borrowing it

Nothing to install: this file belongs to opencue/cuecards. 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/opencue/cuecards/main/.agents/skills/vc-chrome-devtools/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/opencue/cuecards

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 vc:chrome-devtools

README.md
[![agentmods](https://agentmods.dev/badge/skills/opencue/cuecards/vc-chrome-devtools.svg)](https://agentmods.dev/skills/opencue/cuecards/vc-chrome-devtools)
Your own site
<a href="https://agentmods.dev/skills/opencue/cuecards/vc-chrome-devtools"><img src="https://agentmods.dev/badge/skills/opencue/cuecards/vc-chrome-devtools.svg" alt="Measured on agentmods" height="20"></a>
Per session 38 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 5,688 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin 91% 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00038 $0.05688
Opus 5 $0.00019 $0.02844
Sonnet 5 $0.00008 $0.01138
Haiku 4.5 $0.00004 $0.00569

Measured 3d ago against content hash 40cd55d728b3, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

vc:chrome-devtools scanned grade A with 1 finding 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 3d ago.

The scan reads SKILL.md. This mod also ships 3 executable files (scripts/__tests__/error-handling.test.js, scripts/__tests__/selector.test.js, scripts/aria-snapshot.js), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

# Netscape format (from curl/wget):
Origin

This is a copy

91% identical to ck:chrome-devtools — 67 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.

.agents/skills/vc-chrome-devtools/SKILL.md · 635 lines

How it starts

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

Chrome DevTools Agent Skill

Browser automation via Puppeteer scripts with persistent sessions. All scripts output JSON.

Skill Location

Skills can exist in project-scope or user-scope. Priority: project-scope > user-scope.

# Detect skill location (no cd needed - scripts use __dirname for paths)
SKILL_DIR=""
if [ -d ".Codex/skills/chrome-devtools/scripts" ]; then
  SKILL_DIR=".Codex/skills/chrome-devtools/scripts"
elif [ -d "$HOME/.Codex/skills/chrome-devtools/scripts" ]; then
  SKILL_DIR="$HOME/.Codex/skills/chrome-devtools/scripts"
fi
# Run scripts with full path: node "$SKILL_DIR/script.js" --args

Choosing Your Approach

Scenario Approach
Source-available sites Read source code first, write selectors directly
Unknown layouts Use aria-snapshot.js for semantic discovery
Visual inspection Take screenshots to verify rendering
Debug issues Collect console logs, analyze with session storage
Accessibility audit Use ARIA snapshot for semantic structure analysis

Project-Specific Setup

For Flowser-specific connection patterns and when to prefer chrome-devtools over agent-browser or docker exec, see process/context/tests/all-tests.md in the consuming repo. This skill file is a generic tool reference only.

Automation Browsing Running Mode

Browser visibility is resolved automatically by resolveHeadless() in lib/browser.js:

Environment Default Why
macOS / Windows Headed (visible) Better debugging, OAuth login support
Linux / WSL Headless Servers typically have no display
CI (CI, GITHUB_ACTIONS, GITLAB_CI, JENKINS_URL env vars) Headless No display available

Override with --headless true or --headless false on any script.

  • Run multiple scripts/sessions in parallel to simulate real user interactions.
  • Run multiple scripts/sessions in parallel to simulate different device types (mobile, tablet, desktop).

Read the full file on GitHub · 635 lines

Files

What ships with it

60 files 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. 3d ago First seen · 635 lines · 38 tokens per session scan A 40cd55d728b3

Subscribe to this mod's changes

vc:chrome-devtools is a skill published in the GitHub repository opencue/cuecards (5 stars, last pushed today), licensed MIT. It adds 38 tokens to every session and 5,688 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). It is 91% identical to ck:chrome-devtools, differing in 67 lines, and is treated as a copy.

Browser automationClaude CodeDebuggingai-agentsai-codinganthropicclaudecli
Related

Other skills, from other repositories

atomic-debug

Hypothesis-driven debugging skill. Use when a bug, test failure, crash, or unexpected behavior is reported. Auto-trigger on error pastes or "broken/doesn't work/failing" language. Explicit invocation: /atomic-debug. Output: symptom statement → hypothesis table → cheapest test first → root cause. No symptom-patching.…

damusix/atomic-claude · 114 tokens

system-health

Suggest whether the machine needs a DISK or MEMORY cleanup — and catch the case where Heimdall ITSELF is the hog (runaway orphaned python from the presence keeper). Use when the machine is slow / swapping / laggy, disk or "System Data" is full, memory is exhausted, at the start of a long session, or when the user asks…

randomittin/heimdall · 102 tokens

debug

Structured debugging workflow for investigating issues.

SpaceMalamute/ai-rules · 8 tokens

fix-issue

Analyze and fix a GitHub issue with structured workflow.

SpaceMalamute/ai-rules · 14 tokens

stuck

Diagnose frozen, stuck, or slow Qwen Code sessions on this machine. Scans for problematic processes, high CPU/memory usage, hung subprocesses, and debug logs. Use /stuck or /stuck to focus on a specific process.

QwenLM/qwen-code · 57 tokens

structured-debugging

Hypothesis-driven debugging methodology for hard bugs. Use this skill whenever you're investigating non-trivial bugs, unexpected behavior, flaky tests, or tracing issues through complex systems. Activate proactively when debugging requires more than a quick glance — especially when the first attempt at a fix didn't…

QwenLM/qwen-code · 85 tokens