Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Agent Browser Jau771
v1.0.0A fast Rust-based headless browser automation CLI with Node.js fallback that enables AI agents to navigate, click, type, and snapshot pages via structured co...
⭐ 0· 56·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
The SKILL.md describes a headless-browser CLI and the declared requirement (node, npm) matches npm-based installation. However the description asserts a 'Rust-based' implementation with a Node.js fallback while all install instructions use npm/pnpm/git. The registry skill name ('Agent Browser Jau771'), the SKILL.md name ('Agent Browser'), and the _meta.json ownerId/slug differ from the registry metadata — reducing traceability. These mismatches are explainable (packaging choices, copied docs), but they are inconsistent with a clean, verifiable package.
Instruction Scope
Runtime instructions are limited to running the agent-browser CLI commands (open, snapshot, click, fill, screenshot, record, etc.). The SKILL.md does not instruct the agent to read unrelated system files, environment variables, or to send data to unexpected remote endpoints. Note: installation commands (npm install -g, agent-browser install --with-deps) can run arbitrary postinstall scripts; the SKILL.md does not show what those do.
Install Mechanism
This is an instruction-only skill (no install spec). The docs instruct users to run 'npm install -g agent-browser' or to 'git clone' + 'pnpm build' — both reasonable. But the skill's declared required binaries omit git and pnpm even though the From Source steps require them. 'agent-browser install --with-deps' implies the package may download or extract additional dependencies during install; the SKILL.md doesn't disclose what gets fetched or from where.
Credentials
The skill declares no required environment variables or credentials, which aligns with the documented CLI usage. The CLI can be used to set headers, basic auth, upload files, and access cookies/storage at runtime — normal for a browser automation tool — but those operations require user-supplied data and are not automatically requested by the skill.
Persistence & Privilege
always is false and there is no install spec that writes to agent configuration; this instruction-only skill does not request permanent presence or elevated platform privileges.
What to consider before installing
Before installing or granting this skill broad access: 1) Verify the upstream project and publisher — check the agent-browser package on the npm registry and the referenced GitHub repo to confirm authorship and recent releases. 2) Inspect the package's postinstall scripts and the 'agent-browser install' step (it may download native binaries or run build scripts). 3) Note the metadata mismatches (different ownerIds/slug and missing homepage/source) — treat them as a signal to verify origin. 4) Avoid installing globally on a production machine; test in an isolated environment or container. 5) If you need to use credentials with the CLI, supply them only at runtime and avoid storing sensitive secrets in global or agent-accessible locations. 6) If you want higher assurance, ask the publisher to provide a reproducible release (GitHub release with checksums) or supply the exact npm package name/version and its integrity hash for verification.Like a lobster shell, security has layers — review code before you run it.
latestvk97908rws9ygy8pck7ptq10av583g6sy
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🌐 Clawdis
Binsnode, npm