Agent skill

Nodetool Browser Agent

Build a NodeTool browser automation agent for navigation, extraction, forms, or multi-step web tasks.

AGPL-3.0Auto-check passedProductivity & Automation

Install Nodetool Browser Agent

skills CLI

$ npx skills add nodetool-ai/nodetool --skill nodetool-browser-agent -a claude-code

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

GitHub CLI

$ gh skill install nodetool-ai/nodetool nodetool-browser-agent --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/nodetool-ai/nodetool.git skills-src && mkdir -p .claude/skills && cp -r skills-src/packages/system-skills/nodetool-browser-agent .claude/skills/nodetool-browser-agent && 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/

Paste into Claude Code

Install the "nodetool-browser-agent" agent skill from https://github.com/nodetool-ai/nodetool/tree/main/packages/system-skills/nodetool-browser-agent into .claude/skills/nodetool-browser-agent/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nodetool-browser-agent", 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

$skill-installer install https://github.com/nodetool-ai/nodetool/tree/main/packages/system-skills/nodetool-browser-agent

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

skills CLI

$ npx skills add nodetool-ai/nodetool --skill nodetool-browser-agent -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install nodetool-ai/nodetool nodetool-browser-agent --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/nodetool-ai/nodetool.git skills-src && mkdir -p .agents/skills && cp -r skills-src/packages/system-skills/nodetool-browser-agent .agents/skills/nodetool-browser-agent && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "nodetool-browser-agent" agent skill from https://github.com/nodetool-ai/nodetool/tree/main/packages/system-skills/nodetool-browser-agent into .agents/skills/nodetool-browser-agent/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nodetool-browser-agent", 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.

skills CLI

$ npx skills add nodetool-ai/nodetool --skill nodetool-browser-agent -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install nodetool-ai/nodetool nodetool-browser-agent --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/nodetool-ai/nodetool.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/packages/system-skills/nodetool-browser-agent .cursor/skills/nodetool-browser-agent && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "nodetool-browser-agent" agent skill from https://github.com/nodetool-ai/nodetool/tree/main/packages/system-skills/nodetool-browser-agent into .cursor/skills/nodetool-browser-agent/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nodetool-browser-agent", 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

$ gemini skills install https://github.com/nodetool-ai/nodetool.git --path packages/system-skills/nodetool-browser-agent

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add nodetool-ai/nodetool --skill nodetool-browser-agent -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install nodetool-ai/nodetool nodetool-browser-agent --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/nodetool-ai/nodetool.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/packages/system-skills/nodetool-browser-agent .gemini/skills/nodetool-browser-agent && rm -rf skills-src

Use ~/.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/

Paste into Gemini CLI

Install the "nodetool-browser-agent" agent skill from https://github.com/nodetool-ai/nodetool/tree/main/packages/system-skills/nodetool-browser-agent into .gemini/skills/nodetool-browser-agent/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nodetool-browser-agent", 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.

GitHub CLI

$ gh skill install nodetool-ai/nodetool nodetool-browser-agent

Installs 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).

skills CLI

$ npx skills add nodetool-ai/nodetool --skill nodetool-browser-agent -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/nodetool-ai/nodetool.git skills-src && mkdir -p .github/skills && cp -r skills-src/packages/system-skills/nodetool-browser-agent .github/skills/nodetool-browser-agent && rm -rf skills-src

Use ~/.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/

Paste into GitHub Copilot

Install the "nodetool-browser-agent" agent skill from https://github.com/nodetool-ai/nodetool/tree/main/packages/system-skills/nodetool-browser-agent into .github/skills/nodetool-browser-agent/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nodetool-browser-agent", 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.

skills CLI

$ npx skills add nodetool-ai/nodetool --skill nodetool-browser-agent -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install nodetool-ai/nodetool nodetool-browser-agent --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/nodetool-ai/nodetool.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/packages/system-skills/nodetool-browser-agent .opencode/skills/nodetool-browser-agent && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "nodetool-browser-agent" agent skill from https://github.com/nodetool-ai/nodetool/tree/main/packages/system-skills/nodetool-browser-agent into .opencode/skills/nodetool-browser-agent/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nodetool-browser-agent", 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: nodetool-browser-agent
GitHub stars: 560
Token cost: ~1k tokens
SKILL.md length: 305 words
Files: 1
Skills in repo: 127
Repo updated: Oct 9, 2026
First seen: Oct 7, 2026
Licence: AGPL-3.0

At a glance

Build a NodeTool browser automation agent for navigation, extraction, forms, or multi-step web tasks.

Tasks that involve Browser automation
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Nodetool Browser Agent is an agent skill from nodetool-ai/nodetool. Build a NodeTool browser automation agent for navigation, extraction, forms, or multi-step web tasks.

Its SKILL.md is about 1k 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 Productivity & Automation, covering Browser automation. The repository describes itself as: Agent-first Creative Workspace. The licence is AGPL-3.0.

When your agent uses it

Tasks that involve Browser automation

Example prompts

“/nodetool-browser-agent”

What it can do on your machine

Read from SKILL.md and the folder at commit 58765d3. 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
No scripts in the folder and no shell commands in SKILL.md (its code samples are bash and typescript).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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

Nodetool Browser Agent loads about 1k tokens when it runs. Until then it costs about 31 tokens; SKILL.md has 305 words of instructions outside code blocks.

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

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 nodetool-ai/nodetool at commit 58765d3, republished under its AGPL-3.0 licence (© nodetool-ai). 305 words, ~1,026 tokens.

Download SKILL.mdSave it as .claude/skills/nodetool-browser-agent/SKILL.md (or your agent's skills folder).

name: nodetool-browser-agent
description: Build a NodeTool browser automation agent for navigation, extraction, forms, or multi-step web tasks.
featured: true

You help users create NodeTool agents configured for browser automation — AI-powered web agents that navigate, interact with, and extract data from websites using natural-language task descriptions.

Architecture

Browser automation in NodeTool uses the agent system. An agent equipped with the browser tool can navigate pages, capture screenshots, download files, and extract content as part of a planned, multi-step task.

Task description → Agent → (Plan steps → Use browser tools → Extract/interact → Report) → Result

Available Browser Tools

These are the web-related tools the default agent belt offers:

Tool name	Description
`browser`	Fetch and render web page content (executes JavaScript), extract text/links
`screenshot`	Capture a screenshot of a page
`download_file`	Download a file from a URL into the workspace
`web_search`	Web search to discover URLs
`google_news` / `google_images`	News / image search
`http_request`	Raw HTTP GET/POST for APIs and simple fetches

There are no dom_examine, dom_search, or dom_extract tools. The browser tool handles rendering and content extraction; instruct the agent in natural language (e.g. "extract every product title and price") and pair it with write_file to save structured results.

CLI Usage

nodetool agent takes arguments only — there is no config file. Put the instructions in the objective. The CLI always runs the default toolbelt.

bash

# Scrape a page
nodetool agent run -p openai -m gpt-5.4 \
  --objective "Go to example.com, extract every product name and price, and save them as JSON with write_file"

# Research a topic — final answer to stdout, trace to stderr
nodetool agent run -p openai -m gpt-5.4 \
  --objective "Research the latest developments in WebAssembly. Search for sources, browse the promising ones, and compile a structured report." \
  > research-report.md

# Compare prices
nodetool agent run -p openai -m gpt-5.4 \
  --objective "Compare the price, availability, and shipping of <product> across three retailers, then recommend the best deal"

# Objective via stdin
echo "Screenshot example.com and describe the layout" | \
  nodetool agent run -p openai -m gpt-5.4

Browser Agent as a Workflow Node

For visual workflows (and the DSL), there is a dedicated BrowserAgent node (agents.browserAgent in @nodetool-ai/dsl). It runs a browsing agent inside a graph and returns the extracted text. Use this when browsing is one step of a larger pipeline rather than a standalone CLI run.

Programmatic Usage (TypeScript)

typescript

import { Agent } from "@nodetool-ai/agents";
import { BrowserTool, ScreenshotTool, DownloadFileTool } from "@nodetool-ai/agents";
import { ProcessingContext, FileStorageAdapter } from "@nodetool-ai/runtime";

const agent = new Agent({
  name: "browser-agent",
  objective: "Extract product listings from example.com",
  provider: openaiProvider,
  model: "gpt-5.4",
  tools: [new BrowserTool(), new ScreenshotTool(), new DownloadFileTool()],
  workspace: "/tmp/browser-output",
  maxSteps: 15,
});

const ctx = new ProcessingContext({
  jobId: `browser-${Date.now()}`,
  userId: "1",
  workspaceDir: "/tmp/browser-output",
  workspaceStorage: new FileStorageAdapter("/tmp/browser-output"),
});

for await (const message of agent.execute(ctx)) {
  if (message.type === "chunk") process.stdout.write(message.content);
}

Tips

Describe extraction in natural language — the browser tool returns page content; let the model parse it. Pair with write_file to persist results.
Use screenshot to debug visual state or verify a page loaded.
Set max_steps higher (15-20) for multi-page tasks.
Combine with google_search when the agent needs to discover URLs first.
Use http_request for JSON APIs — it's faster and cheaper than full page rendering.

Files

Just SKILL.md in packages/system-skills/nodetool-browser-agent of nodetool-ai/nodetool.

Open the folder on GitHubat commit 58765d3

Compare with similar skills

Nodetool Browser Agent 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.

Nodetool Browser Agent compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Nodetool Browser Agent this skillnodetool-ai/nodetool	560	—	~1k	Automated safety check: Pass	AGPL-3.0	today
Agent Browserquran/quran.com-frontend-next	1.9k	40 repos	~3.3k	Automated safety check: Pass	None	5 mo ago
Dev-Browser CLI AutomationSawyerHood/dev-browser	6.7k	1 repos	~455	Automated safety check: Pass	MIT	1 mo ago
Browser Automationopenclaw/openclaw	392k	—	~2.9k	Automated safety check: Pass	MIT	today
Camoufox CLIBin-Huang/camoufox-cli	350	1 repos	~4.5k	Automated safety check: Pass	MIT	8 days ago
BrowserVibiumDev/vibium	2.9k	—	~4.8k	Automated safety check: Pass	Apache-2.0	yesterday

Similar skills

Agent Browser
quran/quran.com-frontend-next
Automates browser interactions for web testing, form filling, screenshots, and data extraction.
1.9k GitHub starsUsed in 40 repos~3.3k tokens
Productivity & AutomationAuto-check passed
Dev-Browser CLI Automation
SawyerHood/dev-browser
Browser automation with persistent named pages via the dev-browser CLI. Use when users ask to navigate websites, fill forms, take screenshots, extract web…
6.7k GitHub starsUsed in 1 repo~455 tokens
Productivity & AutomationAuto-check passed
Browser Automation
openclaw/openclaw
A skill your agent uses when controlling web pages with the OpenClaw browser tool, especially multi-step flows, login checks, tab management, or recovery from stale refs/timeouts.
392k GitHub stars~2.9k tokensUpdated today
Productivity & AutomationAuto-check passed
Camoufox CLI
Bin-Huang/camoufox-cli
Anti-detect browser automation CLI & Skills for AI agents. An agent skill from Bin-Huang/camoufox-cli.
350 GitHub starsUsed in 1 repo~4.5k tokens
Productivity & AutomationAuto-check passed
Browser
VibiumDev/vibium
Automate browsers with the Vibium CLI. An agent skill from VibiumDev/vibium.
2.9k GitHub stars~4.8k tokensUpdated yesterday
Productivity & AutomationAuto-check passed
Use Agent Browser For Airi
moeru-ai/airi
Test AIRI display-model imports with agent-browser across stage-tamagotchi Electron, stage-web, and stage-pocket mobile web layouts.
50k GitHub stars~1.1k tokensUpdated today
Productivity & AutomationAuto-check passed

More from nodetool-ai/nodetool

All 127 skills in this repo

Beat Sync Editing
nodetool-ai/nodetool
Cut a NodeTool timeline to music and shape its pacing — detect the beat grid, place cuts on phrases, pick a cut type, build speed ramps with time remap, and give the piece an arc.
560 GitHub stars~2.6k tokensUpdated today
Auto-check passed
Caption Titles
nodetool-ai/nodetool
Add and animate a consistent text layer on an existing NodeTool timeline.
560 GitHub stars~1.9k tokensUpdated today
Auto-check passed
Color Motion
nodetool-ai/nodetool
Choose and animate colour on a NodeTool timeline, including shape and text gradients, colour grades, 3D LUTs, and dither.
560 GitHub stars~2.3k tokensUpdated today
Auto-check passed
Commercial Beat Sheet
nodetool-ai/nodetool
Write a shootable, precisely timed commercial beat sheet and store it as a NodeTool storyboard, with a consistent entity roster behind every shot.
560 GitHub stars~4.6k tokensUpdated today
Auto-check passed
Elevenlabs Audio Prompting
nodetool-ai/nodetool
Direct ElevenLabs speech, dialogue, sound effects and music — the bracketed audio tags v3 acts on and why the voice decides whether a tag lands, stability as the delivery dial, punctuation instead…
560 GitHub stars~1.9k tokensUpdated today
Auto-check passed
Frame Composition
nodetool-ai/nodetool
Stage the frame on a NodeTool timeline — grids, focal placement, safe areas per aspect ratio, depth layers and parallax, camera moves, and where elements enter and leave.
560 GitHub stars~3.5k tokensUpdated today
Auto-check passed

Questions about Nodetool Browser Agent

What does Nodetool Browser Agent do?

Build a NodeTool browser automation agent for navigation, extraction, forms, or multi-step web tasks. Nodetool Browser Agent is an agent skill from nodetool-ai/nodetool. Build a NodeTool browser automation agent for navigation, extraction, forms, or multi-step web tasks.

When should I use Nodetool Browser Agent?

Nodetool Browser Agent fits situations like: tasks that involve Browser automation.

How do I install Nodetool Browser Agent in Claude Code?

Run `npx skills add nodetool-ai/nodetool --skill nodetool-browser-agent -a claude-code`. Or copy the skill folder (packages/system-skills/nodetool-browser-agent in nodetool-ai/nodetool) into .claude/skills/nodetool-browser-agent in your project. Claude Code loads it when a task matches its description.

How do I install Nodetool Browser Agent in Codex?

Run `npx skills add nodetool-ai/nodetool --skill nodetool-browser-agent -a codex`. Or copy the skill folder (packages/system-skills/nodetool-browser-agent in nodetool-ai/nodetool) into .agents/skills/nodetool-browser-agent in your project. Codex loads it when a task matches its description.

Can I use Nodetool Browser Agent 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 nodetool-ai/nodetool --skill nodetool-browser-agent -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/nodetool-browser-agent, .gemini/skills/nodetool-browser-agent, .github/skills/nodetool-browser-agent and .opencode/skills/nodetool-browser-agent in your project.

What does Nodetool Browser Agent need to run?

SKILL.md names no scripts, command-line tools or credentials: Nodetool Browser Agent is instructions for the agent only.

Does Nodetool Browser Agent access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Nodetool Browser Agent 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 Nodetool Browser Agent use?

Nodetool Browser Agent is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Nodetool Browser Agent use?

About 1k tokens (SKILL.md is roughly 4.1k 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 Nodetool Browser Agent?

Skills that share tags, products or a category with Nodetool Browser Agent: Agent Browser (quran/quran.com-frontend-next, 1.9k stars), Dev-Browser CLI Automation (SawyerHood/dev-browser, 6.7k stars), Browser Automation (openclaw/openclaw, 392k stars) and Camoufox CLI (Bin-Huang/camoufox-cli, 350 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Nodetool Browser Agent?

nodetool-ai (a GitHub organization) maintains it in nodetool-ai/nodetool, which has 560 GitHub stars. The repository holds 127 skills in this directory. The repository was last updated on October 9, 2026.

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

Install Nodetool Browser Agent

Facts

At a glance

What it does

When your agent uses it

Example prompts

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Architecture

Available Browser Tools

CLI Usage

Browser Agent as a Workflow Node

Programmatic Usage (TypeScript)

Tips

Files

Compare with similar skills

Similar skills

More from nodetool-ai/nodetool

Related

Questions about Nodetool Browser Agent