Agent skill

Browser Verify

by Mr-Quin in Mr-Quin/danmaku-anywhere

A skill your agent uses when an extension change needs exploration in a real browser — finding selectors, watching a flow, reading console or network.

Custom licenceAuto-check passedTesting & QA

Install Browser Verify

skills CLI
$ npx skills add Mr-Quin/danmaku-anywhere --skill browser-verify -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Mr-Quin/danmaku-anywhere browser-verify --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/Mr-Quin/danmaku-anywhere.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/browser-verify .claude/skills/browser-verify && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
browser-verify
GitHub stars
547
Token cost
~1.5k tokens
SKILL.md length
598 words
Files
1
Skills in repo
9
Repo updated
First seen
Licence
Custom licence

At a glance

A skill your agent uses when an extension change needs exploration in a real browser — finding selectors, watching a flow, reading console or network.

  • Works in 7 steps: Preflight → Drive it → Turn what you found into spec code → …
  • An extension change needs exploration in a real browser — finding selectors
  • SKILL.md covers 0. Preflight, 1. Drive it, 2. Turn what you found into… and 3. Seed state through the dev…, plus 4 more sections
  • Calls npx and pnpm

What it does

Browser Verify is an agent skill from Mr-Quin/danmaku-anywhere. Use when an extension change needs exploration in a real browser — finding selectors, watching a flow, reading console or network. Drives the agent's own headless Chromium through the Playwright CLI. Exploration only; the verification that counts is a spec (see e2e-spec).

Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Testing & QA, covering End-to-end testing and Browser testing. It works with Playwright and Chrome Extensions. The repository describes itself as: 一个可以给几乎任何视频网站添加弹幕的开源软件 | An open source solution to add danmaku to almost every video website.

When your agent uses it

  • An extension change needs exploration in a real browser — finding selectors
  • Watching a flow
  • Reading console

Example prompts

  • “/browser-verify”

Requirements

  • Node.js

Workflow steps

7 steps, taken from the step headings in SKILL.md.

  1. Preflight
  2. Drive it
  3. Turn what you found into spec code
  4. Seed state through the dev API
  5. Inspect
  6. After a rebuild, reload in place
  7. Tear down

What it can do on your machine

Read from SKILL.md and the folder at commit d2d6d41. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • npx
    • pnpm

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use npx and pnpm, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Browser Verify loads about 1.5k tokens when it runs. Until then it costs about 72 tokens; SKILL.md has 598 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~72
When it runs · the whole SKILL.md, loaded when a task matches
~1.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 598 words (~1,489 tokens).

“This skill is for the part of the loop where you don't yet know what to assert: finding a selector, watching what a flow actually does, reading a console error, checking a request.”

— opening of SKILL.md by Mr-Quin, Custom licence
name
browser-verify

Read the full SKILL.md on GitHub

Files

Just SKILL.md in .claude/skills/browser-verify of Mr-Quin/danmaku-anywhere.

Open the folder on GitHubat commit d2d6d41

Compare with similar skills

Browser Verify next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Browser Verify compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Browser Verify this skillMr-Quin/danmaku-anywhere547—~1.5kAutomated safety check: PassCustom licence
Web Application Testinganthropics/skills180k51 repos~966Automated safety check: PassApache-2.0
playwright-cli Browser Automationgithub/gh-aw5.3k23 repos~2.8kAutomated safety check: PassMIT
Write and Verify Playwright Testsappsmithorg/appsmith41k—~2.9kAutomated safety check: NotesApache-2.0
Cucumber and Playwright E2E Testslanggenius/dify158k—~682Automated safety check: PassCustom licence
E2E Testinglangflow-ai/langflow156k—~3.3kAutomated safety check: PassMIT

Similar skills

  • Web Application Testing

    anthropics/skills

    Official

    Tests local web applications with Python Playwright scripts, checking frontend behavior, capturing screenshots and reading browser console logs.

    180k GitHub starsUsed in 51 repos~966 tokens
    Testing & QAAuto-check passed
  • Official

    Drives a real browser from the command line with playwright-cli to open pages, interact, mock requests, save state and work with Playwright tests.

    5.3k GitHub starsUsed in 23 repos~2.8k tokens
    Testing & QAAuto-check passed
  • Writes a Playwright end-to-end test from a prompt, runs it against a live Appsmith deployment and retries with fixes up to three times until it passes.

    41k GitHub stars~2.9k tokensUpdated today
    Testing & QAAuto-check: notes
  • Guides changes and reviews of the Cucumber and Playwright end-to-end suite under `e2e/`: feature files, step definitions, support code, tags, locators and assertions.

    158k GitHub stars~682 tokensUpdated today
    Testing & QAAuto-check passed
  • E2E Testing

    langflow-ai/langflow

    Write and review Playwright E2E tests for Langflow. An agent skill from langflow-ai/langflow.

    156k GitHub stars~3.3k tokensUpdated today
    Testing & QAAuto-check passed
  • Handsontable Playwright E2E Tests

    handsontable/handsontable

    Guides writing and changing Playwright end-to-end tests for Handsontable using page objects, data-testid hooks and deterministic waits.

    22k GitHub stars~1.7k tokensUpdated today
    Testing & QAAuto-check passed

More from Mr-Quin/danmaku-anywhere

All 9 skills in this repo
  • Babysit PR

    Mr-Quin/danmaku-anywhere

    A skill your agent uses to monitor an open PR for AI/bot review comments, evaluate them critically, push fixes for real issues, and resolve threads — capped at a sensible duration so it…

    547 GitHub stars~1.3k tokensUpdated 1 mo ago
    Auto-check passed
  • I18n

    Mr-Quin/danmaku-anywhere

    A skill your agent uses when adding or changing user-facing strings in the extension (i18n.t calls or locale JSON) under packages/danmaku-anywhere.

    547 GitHub stars~689 tokensUpdated 1 mo ago
    Auto-check passed
  • Preview Build

    Mr-Quin/danmaku-anywhere

    A skill your agent uses when you need to load a specific published preview/nightly extension build into the agent's browser by run-number, branch name, or tag.

    547 GitHub stars~886 tokensUpdated 1 mo ago
    Auto-check passed
  • Reviewing AI Feedback

    Mr-Quin/danmaku-anywhere

    A skill your agent uses when evaluating review comments from AI reviewers (gemini-code-assist, copilot-pull-request-reviewer) on a PR.

    547 GitHub stars~901 tokensUpdated 1 mo ago
    Auto-check passed
  • Specs In Clickup

    Mr-Quin/danmaku-anywhere

    A skill your agent uses when finishing a brainstorm, writing a design spec, or producing an implementation plan in this project.

    547 GitHub stars~663 tokensUpdated 1 mo ago
    Auto-check passed
  • Worktree Tab

    Mr-Quin/danmaku-anywhere

    A skill your agent uses to open a fresh Claude session in a new terminal tab for a da-dev worktree, after scripts/da-bootstrap.mjs prints its READY block.

    547 GitHub stars~632 tokensUpdated 1 mo ago
    Auto-check passed

Categories

Questions about Browser Verify

What does Browser Verify do?

A skill your agent uses when an extension change needs exploration in a real browser — finding selectors, watching a flow, reading console or network. Browser Verify is an agent skill from Mr-Quin/danmaku-anywhere. Use when an extension change needs exploration in a real browser — finding selectors, watching a flow, reading console or network.

When should I use Browser Verify?

Browser Verify fits situations like: an extension change needs exploration in a real browser — finding selectors; watching a flow; reading console.

How do I install Browser Verify in Claude Code?

Run `npx skills add Mr-Quin/danmaku-anywhere --skill browser-verify -a claude-code`. Or copy the skill folder (.claude/skills/browser-verify in Mr-Quin/danmaku-anywhere) into .claude/skills/browser-verify in your project. Claude Code loads it when a task matches its description.

How do I install Browser Verify in Codex?

Run `npx skills add Mr-Quin/danmaku-anywhere --skill browser-verify -a codex`. Or copy the skill folder (.claude/skills/browser-verify in Mr-Quin/danmaku-anywhere) into .agents/skills/browser-verify in your project. Codex loads it when a task matches its description.

Can I use Browser Verify in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Mr-Quin/danmaku-anywhere --skill browser-verify -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/browser-verify, .gemini/skills/browser-verify, .github/skills/browser-verify and .opencode/skills/browser-verify in your project.

What does Browser Verify need to run?

Going by SKILL.md and its folder, Browser Verify needs the command-line tools its instructions call (npx and pnpm). Our summary lists: Node.js.

Does Browser Verify access the network?

SKILL.md contains no URLs. Its commands use npx, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Browser Verify safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Browser Verify use?

Browser Verify has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.

How many tokens does Browser Verify use?

About 1.5k tokens (SKILL.md is roughly 6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Browser Verify?

Skills that share tags, products or a category with Browser Verify: Web Application Testing (anthropics/skills, 180k stars), playwright-cli Browser Automation (github/gh-aw, 5.3k stars), Write and Verify Playwright Tests (appsmithorg/appsmith, 41k stars) and Cucumber and Playwright E2E Tests (langgenius/dify, 158k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Browser Verify?

Mr-Quin (a GitHub user) maintains it in Mr-Quin/danmaku-anywhere, which has 547 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on September 7, 2026.

Source: Mr-Quin/danmaku-anywhere on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.