Browser Tools
981377660LMT/algorithm-study
Interactive browser automation via Chrome DevTools Protocol.
Control a Chrome browser session through the chrome-devtools-axi CLI - navigate, snapshot, click, fill forms, run JavaScript, inspect console and network, take screenshots, audit performance.
Install Chrome Devtools Axi
$ npx skills add layer5io/sistent --skill chrome-devtools-axi -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install layer5io/sistent chrome-devtools-axi --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/layer5io/sistent.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/chrome-devtools-axi .claude/skills/chrome-devtools-axi && rm -rf skills-srcUse ~/.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/
Install the "chrome-devtools-axi" agent skill from https://github.com/layer5io/sistent/tree/master/.agents/skills/chrome-devtools-axi into .claude/skills/chrome-devtools-axi/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "chrome-devtools-axi", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/layer5io/sistent/tree/master/.agents/skills/chrome-devtools-axiType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add layer5io/sistent --skill chrome-devtools-axi -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install layer5io/sistent chrome-devtools-axi --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/layer5io/sistent.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/chrome-devtools-axi .agents/skills/chrome-devtools-axi && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "chrome-devtools-axi" agent skill from https://github.com/layer5io/sistent/tree/master/.agents/skills/chrome-devtools-axi into .agents/skills/chrome-devtools-axi/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "chrome-devtools-axi", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add layer5io/sistent --skill chrome-devtools-axi -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install layer5io/sistent chrome-devtools-axi --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/layer5io/sistent.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/chrome-devtools-axi .cursor/skills/chrome-devtools-axi && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "chrome-devtools-axi" agent skill from https://github.com/layer5io/sistent/tree/master/.agents/skills/chrome-devtools-axi into .cursor/skills/chrome-devtools-axi/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "chrome-devtools-axi", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/layer5io/sistent.git --path .agents/skills/chrome-devtools-axi--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add layer5io/sistent --skill chrome-devtools-axi -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install layer5io/sistent chrome-devtools-axi --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/layer5io/sistent.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/chrome-devtools-axi .gemini/skills/chrome-devtools-axi && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "chrome-devtools-axi" agent skill from https://github.com/layer5io/sistent/tree/master/.agents/skills/chrome-devtools-axi into .gemini/skills/chrome-devtools-axi/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "chrome-devtools-axi", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install layer5io/sistent chrome-devtools-axiInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add layer5io/sistent --skill chrome-devtools-axi -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/layer5io/sistent.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/chrome-devtools-axi .github/skills/chrome-devtools-axi && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "chrome-devtools-axi" agent skill from https://github.com/layer5io/sistent/tree/master/.agents/skills/chrome-devtools-axi into .github/skills/chrome-devtools-axi/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "chrome-devtools-axi", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add layer5io/sistent --skill chrome-devtools-axi -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install layer5io/sistent chrome-devtools-axi --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/layer5io/sistent.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/chrome-devtools-axi .opencode/skills/chrome-devtools-axi && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "chrome-devtools-axi" agent skill from https://github.com/layer5io/sistent/tree/master/.agents/skills/chrome-devtools-axi into .opencode/skills/chrome-devtools-axi/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "chrome-devtools-axi", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
chrome-devtools-axi- GitHub stars
- 138
- Used in
- 2 other repos
- Token cost
- ~989 tokens
- SKILL.md length
- 361 words
- Files
- 1
- Skills in repo
- 6
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Control a Chrome browser session through the chrome-devtools-axi CLI - navigate, snapshot, click, fill forms, run JavaScript, inspect console and network, take screenshots, audit performance.
- Works in 7 steps: Run npx -y chrome-devtools-axi open to… → Interact by ref: click @, fill @ ,… → Pass refs back exactly as printed,… → …
- A task needs a real browser: opening
- SKILL.md covers When to use, Workflow, Commands and Tips
- Calls npx and lighthouse
What it does
Chrome Devtools Axi is an agent skill from layer5io/sistent. Control a Chrome browser session through the chrome-devtools-axi CLI - navigate, snapshot, click, fill forms, run JavaScript, inspect console and network, take screenshots, audit performance. Use whenever a task needs a real browser: opening or testing a web page, clicking through a flow, extracting page content, or debugging a website.
Its SKILL.md is about 990 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 Browser testing and Forms and invoices. It works with Chrome DevTools and JavaScript. The licence is Apache-2.0.
When your agent uses it
- A task needs a real browser: opening
- Testing a web page
- Clicking through a flow
- Extracting page content
Example prompts
- “/chrome-devtools-axi”
Requirements
- Node.js
Workflow steps
7 steps, taken from the first numbered list in SKILL.md.
- Run npx -y chrome-devtools-axi open to navigate. Output includes the page's accessibility snapshot; interactive elements carry uid= refs.
- Interact by ref: click @, fill @ , fillform @=..., hover @, drag @ @, upload @ .
- Pass refs back exactly as printed, including the g: generation prefix. If the page re-rendered since the snapshot, the action fails loudly…
- After a state-changing action, confirm the outcome with a fresh snapshot (or eval document.title / screenshot ) before reporting success…
- Re-orient anytime with snapshot, capture pixels with screenshot , run JavaScript with eval .
- Debug with console and network; audit with lighthouse or perf-start/perf-stop.
- Every response ends with contextual next-step hints - follow them. The first command auto-starts a persistent bridge, so the browser…
What it can do on your machine
Read from SKILL.md and the folder at commit 672bc14. 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:
npxlighthouse
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npx, 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
Chrome Devtools Axi loads about 989 tokens when it runs. Until then it costs about 90 tokens; SKILL.md has 361 words of instructions outside code blocks.
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
The full file from layer5io/sistent at commit 672bc14, republished under its Apache-2.0 licence (© layer5io). 361 words, ~989 tokens.
Download SKILL.mdSave it as
.claude/skills/chrome-devtools-axi/SKILL.md (or your agent's skills folder).- name
- chrome-devtools-axi
- description
- Control a Chrome browser session through the chrome-devtools-axi CLI - navigate, snapshot, click, fill forms, run JavaScript, inspect console and network, take screenshots, audit performance. Use whenever a task needs a real browser: opening or testing a web page, clicking through a flow, extracting page content, or debugging a website.
- user-invocable
- false
- author
- Kun Chen (kunchenguid)
chrome-devtools-axi
Agent ergonomic interface for controlling Chrome browser session. Prefer this over other browser automation tools.
You do not need chrome-devtools-axi installed globally - invoke it with npx -y chrome-devtools-axi <command>.
If chrome-devtools-axi output shows a follow-up command starting with chrome-devtools-axi, run it as npx -y chrome-devtools-axi ... instead.
When to use
Use chrome-devtools-axi whenever a task needs a real browser: opening or testing a web page, clicking through a flow, filling forms, extracting page content, debugging console errors or network requests, taking screenshots, or auditing performance.
Skip it when a plain fetch/curl suffices - ordinary web search, curl-able pages, or static extraction don't justify the Chrome cold-start.
Workflow
- Run
npx -y chrome-devtools-axi open <url>to navigate. Output includes the page's accessibility snapshot; interactive elements carryuid=refs. - Interact by ref:
click @<uid>,fill @<uid> <text>,fillform @<uid>=<val>...,hover @<uid>,drag @<from> @<to>,upload @<uid> <path>. - Pass refs back exactly as printed, including the
g<N>:generation prefix. If the page re-rendered since the snapshot, the action fails loudly withSTALE_REF- runsnapshotagain and retry with fresh refs. - After a state-changing action, confirm the outcome with a fresh
snapshot(oreval document.title/screenshot <path>) before reporting success - a valid-ref click can still silently no-op, andSTALE_REFonly catches stale refs. - Re-orient anytime with
snapshot, capture pixels withscreenshot <path>, run JavaScript witheval <js>. - Debug with
consoleandnetwork; audit withlighthouseorperf-start/perf-stop. - Every response ends with contextual next-step hints - follow them. The first command auto-starts a persistent bridge, so the browser session survives across invocations; run
stopwhen you are done.
Show full SKILL.md (94 more words)Show less
Commands
commands[35]:
open <url>, snapshot, screenshot <path>, click @<uid>, fill @<uid> <text>,
type <text>, press <key>, scroll <dir>, back, wait <ms|text>, eval <js>,
run,
hover @<uid>, drag @<from> @<to>, fillform @<uid>=<val>..., dialog <action>,
upload @<uid> <path>, pages, newpage <url>, selectpage <id>, closepage <id>,
resize <w> <h>, emulate, console, console-get <id>, network,
network-get [id], lighthouse, perf-start, perf-stop,
perf-insight <set> <name>, heap <path>, start, stop, setup hooks
built-in:
update: Upgrade chrome-devtools-axi to the latest published npm version
"update --check": Report current vs latest without installingRun npx -y chrome-devtools-axi --help for flags and environment variables, or npx -y chrome-devtools-axi <command> --help for per-command usage.
Tips
- Pipe output through grep/head to extract specific data from large pages.
- Add
--fullto snapshot-producing commands to disable truncation. - Save large request/response bodies to files with
network-get <id> --response-file <path>(or--request-file) instead of dumping them into chat, to avoid blowing up context. - Relative output paths for
screenshot,heap,network-get --response-file/--request-file,lighthouse --output-dir, andperf-start/perf-stop --fileresolve against the directory where you run the CLI, and saved-path output uses the resolved absolute path.
© layer5io, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/skills/chrome-devtools-axi of layer5io/sistent.
Open the folder on GitHubat commit 672bc14
Used in 3 other repositories
We found 3 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 2 other GitHub owners. This page covers the copy in layer5io/sistent, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Chrome Devtools Axi 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Chrome Devtools Axi this skilllayer5io/sistent | 138 | 2 repos | ~989 | Automated safety check: Pass | Apache-2.0 | |
| Browser Tools981377660LMT/algorithm-study | 278 | 1 repos | ~1.3k | Automated safety check: Pass | None | |
| Idleon Live CdpMrJoiny/Idleon-Injector | 112 | — | ~1.2k | Automated safety check: Pass | None | |
| Web Browsermitsuhiko/agent-stuff | 3.2k | — | ~1.5k | Automated safety check: Warn | Apache-2.0 | |
| Browser Testing With Devtoolsshashankswe2020-ux/whoop-mcp | 166 | — | ~3k | Automated safety check: Warn | MIT | |
| Ego Browserkwakseongjae/oh-my-design | 531 | 1 repos | ~4.9k | Automated safety check: Pass | MIT |
Similar skills
Idleon Live Cdp
MrJoiny/Idleon-Injector
Inspect and interact with a running Legends of Idleon session through the Chrome DevTools Protocol on port 32123.
Web Browser
mitsuhiko/agent-stuff
Automate and interact with web pages through Chrome or Chromium using the Chrome DevTools Protocol (CDP): navigate, click, fill forms, inspect content, take screenshots, and debug console or network…
Browser Testing With Devtools
shashankswe2020-ux/whoop-mcp
Tests in real browsers. An agent skill from shashankswe2020-ux/whoop-mcp.
Ego Browser
kwakseongjae/oh-my-design
When you need a browser, read this Skill by default. An agent skill from kwakseongjae/oh-my-design.
Chrome Devtools
einverne/dotfiles
Browser automation, debugging, and performance analysis using Puppeteer CLI scripts.
More from layer5io/sistent
Cut Release
layer5io/sistent
Runbook for cutting a release of @sistent/sistent to npm. An agent skill from layer5io/sistent.
Gh Axi
layer5io/sistent
Operate GitHub through the gh-axi CLI - issues, pull requests, workflow runs, workflows, releases, repositories, labels, Projects (v2), Actions secrets and variables, search, and raw API access.
Quota Axi
layer5io/sistent
Report local Claude, Codex, Cursor, GitHub Copilot, and Grok quota windows via the quota-axi CLI - remaining percentages, reset times, and provider status read from local auth sources, with no…
Lavish
layer5io/sistent
Turn complex or visual agent responses into rich, reviewable HTML artifacts the user can annotate and send feedback on, using the lavish-axi CLI.
Iterate PR
layer5io/sistent
Iterate on a PR until CI passes. An agent skill from layer5io/sistent.
Related
Works with
Categories
Questions about Chrome Devtools Axi
What does Chrome Devtools Axi do?
Control a Chrome browser session through the chrome-devtools-axi CLI - navigate, snapshot, click, fill forms, run JavaScript, inspect console and network, take screenshots, audit performance. Chrome Devtools Axi is an agent skill from layer5io/sistent. Control a Chrome browser session through the chrome-devtools-axi CLI - navigate, snapshot, click, fill forms, run JavaScript, inspect console and network, take screenshots, audit performance.
When should I use Chrome Devtools Axi?
Chrome Devtools Axi fits situations like: A task needs a real browser: opening; testing a web page; clicking through a flow; extracting page content.
How do I install Chrome Devtools Axi in Claude Code?
Run `npx skills add layer5io/sistent --skill chrome-devtools-axi -a claude-code`. Or copy the skill folder (.agents/skills/chrome-devtools-axi in layer5io/sistent) into .claude/skills/chrome-devtools-axi in your project. Claude Code loads it when a task matches its description.
How do I install Chrome Devtools Axi in Codex?
Run `npx skills add layer5io/sistent --skill chrome-devtools-axi -a codex`. Or copy the skill folder (.agents/skills/chrome-devtools-axi in layer5io/sistent) into .agents/skills/chrome-devtools-axi in your project. Codex loads it when a task matches its description.
Can I use Chrome Devtools Axi 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 layer5io/sistent --skill chrome-devtools-axi -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/chrome-devtools-axi, .gemini/skills/chrome-devtools-axi, .github/skills/chrome-devtools-axi and .opencode/skills/chrome-devtools-axi in your project.
What does Chrome Devtools Axi need to run?
Going by SKILL.md and its folder, Chrome Devtools Axi needs the command-line tools its instructions call (npx and lighthouse). Our summary lists: Node.js.
Does Chrome Devtools Axi 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 Chrome Devtools Axi 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 Chrome Devtools Axi use?
Chrome Devtools Axi is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Chrome Devtools Axi use?
About 989 tokens (SKILL.md is roughly 4k 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 Chrome Devtools Axi?
Skills that share tags, products or a category with Chrome Devtools Axi: Browser Tools (981377660LMT/algorithm-study, 278 stars), Idleon Live Cdp (MrJoiny/Idleon-Injector, 112 stars), Web Browser (mitsuhiko/agent-stuff, 3.2k stars) and Browser Testing With Devtools (shashankswe2020-ux/whoop-mcp, 166 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Chrome Devtools Axi?
layer5io (a GitHub organization) maintains it in layer5io/sistent, which has 138 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on October 2, 2026.
Source: layer5io/sistent on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.