Fastest Browser Use
Analysis
This browser automation skill is mostly coherent with its scraping purpose, but it explicitly promotes bot-detection evasion and saving/reusing login session cookies, which users should review carefully before installing.
Findings (5)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Checks for instructions or behavior that redirect the agent, misuse tools, execute unexpected code, cascade across systems, exploit user trust, or continue outside the intended task.
### 1. Bypass "Bot Detection" via Human Emulation Simulate mouse jitter and random delays to scrape protected sites.
The skill explicitly instructs agents to evade bot-detection controls and scrape protected sites, which goes beyond ordinary browser automation and may violate site access boundaries.
install:
- kind: brew
formula: rknoche6/tap/fast-browser-use
- kind: cargo
package: fast-browser-useThe skill declares external brew and cargo installation paths, while the registry section says there is no install spec. The install methods are disclosed and purpose-aligned, but metadata under-declaration makes provenance and setup expectations less clear.
var loadReadability = new Function(
The static scan reports dynamic JavaScript construction in the Markdown conversion tool. This appears related to page-content extraction, but dynamic code execution is sensitive in a browser automation package.
Checks whether tool use, credentials, dependencies, identity, account access, or inter-agent boundaries are broader than the stated purpose.
### 3. Login & Cookie Heist Log in manually once, then steal the session for headless automation. fast-browser-use login --url "https://github.com/login" --save-session ./auth.json
The documented workflow saves an authenticated browser session to a local file and later reuses it, which handles account-session material but is not declared as a credential requirement in the registry metadata.
Checks for exposed credentials, poisoned memory or context, unclear communication boundaries, or sensitive data that could leave the user's control.
A browser session manager wrapping `headless_chrome` ... A tool system for common browser operations ... An MCP (Model Context Protocol) server for AI-driven browser automation
The project is designed to expose browser-control tools through MCP for agent use. This is expected for the skill, but MCP browser access can expose page contents and authenticated sessions to connected agents.
