A browser-use guide for opening websites and interacting with pages as a person would, including pages with logins, forms, dynamic content, or bot checks.

Use it to navigate pages, inspect their structure, take screenshots, click controls, and enter text.

It provides a way to work with websites that ordinary search cannot fully read or operate.

web-browse — Skill for Claude Code by LFTPadilla/agent-dev-kit

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add LFTPadilla/agent-dev-kit --skill web-browse

Clone the repo

git clone --depth 1 https://github.com/LFTPadilla/agent-dev-kit

Made for: Claude Code.

Or install dev-skills, the plugin that ships this one along with the rest of its 26 skills, 1 command.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/lftpadilla/agent-dev-kit/web-browse/github.svg)](https://agentmods.dev/skills/lftpadilla/agent-dev-kit/web-browse)

Your own site

<a href="https://agentmods.dev/skills/lftpadilla/agent-dev-kit/web-browse"><img src="https://agentmods.dev/badge/skills/lftpadilla/agent-dev-kit/web-browse/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/lftpadilla/agent-dev-kit/web-browse"><img src="https://agentmods.dev/badge/skills/lftpadilla/agent-dev-kit/web-browse.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 100 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 670 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.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00100	$0.00670
Opus 5.5	$0.00040	$0.00268
Sonnet 5.5	$0.00020	$0.00134
Haiku 4.5	$0.00010	$0.00067

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

Security

Grade A, and why

web-browse 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 1mo 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.

plugins/dev-skills/skills/web-browse/SKILL.md · 65 lines

How it starts

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

Web Browse Skill

Use the browser tool to navigate web pages as a real user.

Mandatory execution rule

Use this skill only when normal brave-search is insufficient: login flows, dynamic pages, forms, buttons, CAPTCHAs, dashboards, or explicit requests to open/navigate a site. For ordinary web search, use brave-search first. Do not tell the user web access is unavailable just because browser interaction is not needed.

Setup

Browser is already configured on Argo:

Chromium at /usr/bin/chromium (no sandbox, host mode)
CDP port: 18800

Browser Tool Quick Reference

Action	When to use
`browser(action="open", url="...")`	Navigate to URL
`browser(action="snapshot", targetId="...")`	Get page structure (aria refs)
`browser(action="screenshot", targetId="...")`	Visual screenshot
`browser(action="act", targetId="...", request={kind:"click", ref:"..."})`	Click element
`browser(action="act", targetId="...", request={kind:"type", ref:"...", text:"..."})`	Type in input
`browser(action="act", targetId="...", request={kind:"press", key:"Enter"})`	Press key

Workflow

Open the URL with browser(action="open", target="host", url="...")
Snapshot to see page structure and get element refs
Act to interact (click, type, scroll, hover)
Repeat until task is done
Close the browser when done

Common Patterns

Login to a site

open → snapshot → find login fields → type credentials → click submit → verify

Extract data from a page

open → snapshot → identify data elements → act to expand/scroll if needed → snapshot → extract

Click through a flow

open → snapshot → click button → wait for navigation → snapshot → click next → ...

Tips

Use compact=true in snapshot for fewer nodes
Use refs="aria" to get stable aria refs for act targets
If a page doesn't load, try adding timeMs=2000 to act for wait
For pages requiring user interaction, use screenshot to see what the agent sees
Headless mode: add headless=true to open if you don't want visible browser
Keep browser open between related actions to avoid re-authenticating

Read the full file on GitHub · 65 lines

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.

1mo ago First seen · 65 lines · 100 tokens per session scan A 9c05a60807e1

Subscribe to this mod's changes

web-browse is a skill published in the GitHub repository LFTPadilla/agent-dev-kit (2 stars, last pushed 27d ago), licensed MIT. It adds 100 tokens to every session and 670 once invoked, about $0.0004 per session on Opus 5.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-08-31.

Browser automation Claude Code Code review LLM agent-skills ai-agents developer-tools skill

visual-aspect-analyzer

Run this as the FINAL review step once you have finished a UI change you can load in a browser — it is the visual-regression gate, run once at the end (not after every edit), and the change is not done until it reports score: 100. It drives a real browser over the page, auto-detects its relevant elements (no…

tale-project/tale · 190 tokens

coding-standards

Applies language-neutral engineering standards when writing or reviewing code, especially around boundaries, failures, domain models, dependencies, tests, and type safety.

iurysza/android-use · 34 tokens

ai-search-hub

Run the AI Search Hub browser automation scripts for Yuanbao, LongCat, Doubao, Qwen, Gemini, Grok, and MiniMax. Use this skill when the user wants to ask one of those sites a prompt, auto-start or attach to a Chrome DevTools session on port 9222, seed an isolated debug browser profile from the user's local browser…

minsight-ai-info/AI-Search-Hub · 102 tokens

code-review

Review a code snippet for bugs, security issues, and style, with concrete fixes. Use when the user shares code and asks for feedback or a review.

TeamDzX/myllm-skills · 34 tokens

lean-audit

Whole-repo audit for over-engineering. Like lean-review, but scans the entire codebase instead of a diff: a ranked list of what to delete, simplify, or replace with stdlib/native equivalents. Use when the user says "audit this codebase", "audit for over-engineering", "what can I delete from this repo", "find bloat"…

utk2103/Prompt-Studio · 98 tokens

lean-review

Code review focused exclusively on over-engineering. Finds what to delete: reinvented standard library, unneeded dependencies, speculative abstractions, dead flexibility. One line per finding: location, what to cut, what replaces it. Use when the user says "review for over-engineering", "what can we delete", "is this…

utk2103/Prompt-Studio · 96 tokens