Skills/ClawHub/openclaw-agent-browser

openclaw-agent-browser@1.0.0

VERIFIED· install only

Publisher claims: "Headless browser automation CLI for AI agents. Use when interacting with websites — navigating pages, filling forms, clicking buttons, taking screenshots, ex..." Observed in sandbox: reads credential files.

Registry ClawHubPublisher bodietron · publishing for 265 daysInstalls 19,560Last detonated 27 min ago
$clawhub install openclaw-agent-browser
WatchReport an issue

Coverage

Install scripts ran; no agent task scenario for this bundle.
Tested
install scripts, with decoy credentials in place · second launch with the clock 45 days ahead · every file read, file written and host contacted by what ran
Not tested
use of the skill by an agent

Is [email protected] safe to install?

KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; install scripts ran; no agent task scenario for this bundle) on 2026-11-18 and scored it 86/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: reads credential files.

Behavior trace

Honeypot run · 2 s · 2 scenarios
t+CategoryObserved action
0.0sprocessinstall script run in the sandbox
0.8sfilesystemread ~/.npmrc
0.8sfilesystemread ~/.npm/_logs · ~/.npm/_cacache/index-v5/3d/cc/3a2d41bb301988dae8cf23b590a464bd3a494781ba0f55a70349387c1e21 · ~/.npm/_cacache/index-v5/c3/ba/8194194aab52102fd953a55f9f4fa9cb13bf81081cd6c94a5dabe3568a46 · ~/.npm/_cacache/index-v5/ba/bb/6a1ecb9bb53685e7a7d2ddb8dfb0ebb6a4f892072e5ba7bf5774bac31567 · ~/.npm/_cacache/index-v5/1a/19/000c23ec93d1c4c3984fcde24dca92e1bc9cf12fadb54ea03e2cbce0feb5 · ~/.npm/_cacache/index-v5/47/c4/8a2a004b22668c9911325f1f2a4de4f30627501a2bb143afbade013f7deb outside project
0.8sfilesystemwrote ~/.npm/_cacache/tmp/80a94984 · ~/.npm/_cacache/index-v5/3d/cc/3a2d41bb301988dae8cf23b590a464bd3a494781ba0f55a70349387c1e21 · ~/.npm/_cacache/tmp/b6142ced · ~/.npm/_cacache/index-v5/c3/ba/8194194aab52102fd953a55f9f4fa9cb13bf81081cd6c94a5dabe3568a46 · ~/.npm/_cacache/tmp/c42861e5 · ~/.npm/_cacache/index-v5/ba/bb/6a1ecb9bb53685e7a7d2ddb8dfb0ebb6a4f892072e5ba7bf5774bac31567
0.8snetworkCONNECT tcp://registry.npmjs.org:443
0.8snetworkCONNECT tcp://registry.npmjs.org:443
0.8snetworkCONNECT tcp://registry.npmjs.org:443
0.8snetworkCONNECT tcp://registry.npmjs.org:443
0.8snetworkCONNECT tcp://registry.npmjs.org:443
0.8snetworkCONNECT tcp://registry.npmjs.org:443
0.8snetworkCONNECT tcp://registry.npmjs.org:443
0.8sprocessexec /usr/local/bin/npm
0.8sprocessexited 243: npm error A complete log of this run can be found in: /tmp/ks-detonate-WrqKpk/setup/home/.npm/_logs/2026-11-18T14_24_36_211Z-debug-0.log
0.8sprocessscript backend runs setup only
0.8sprocessscript backend runs setup only
1.2sprocesssecond launch, clock +45 days, CI unset
2.0sfilesystemread ~/.npmrc
2.0sfilesystemread ~/.npm/_logs · ~/.npm/_cacache/index-v5/3d/cc/3a2d41bb301988dae8cf23b590a464bd3a494781ba0f55a70349387c1e21 · ~/.npm/_cacache/content-v2/sha512/9f/64/f9fce796b9abd1551812d2ba3effe9cbbbc378b3507335c121c6ca761d9713a509a32e1eb4abb755dcf0ea9060e4043fc1a430e4d5e18d4d76f2a1f89646 · ~/.npm/_cacache/index-v5/c3/ba/8194194aab52102fd953a55f9f4fa9cb13bf81081cd6c94a5dabe3568a46 · ~/.npm/_cacache/index-v5/ba/bb/6a1ecb9bb53685e7a7d2ddb8dfb0ebb6a4f892072e5ba7bf5774bac31567 · ~/.npm/_cacache/index-v5/1a/19/000c23ec93d1c4c3984fcde24dca92e1bc9cf12fadb54ea03e2cbce0feb5 outside project
2.0sfilesystemwrote ~/.npm/_cacache/tmp/eb618ebf · ~/.npm/_cacache/index-v5/3d/cc/3a2d41bb301988dae8cf23b590a464bd3a494781ba0f55a70349387c1e21 · ~/.npm/_cacache/tmp/c08b2f29 · ~/.npm/_cacache/tmp/3db7173b · ~/.npm/_cacache/tmp/147185ab · ~/.npm/_cacache/tmp/fc31201c
2.0snetworkCONNECT tcp://registry.npmjs.org:443
2.0snetworkCONNECT tcp://registry.npmjs.org:443
2.0snetworkCONNECT tcp://registry.npmjs.org:443
2.0snetworkCONNECT tcp://registry.npmjs.org:443
2.0snetworkCONNECT tcp://registry.npmjs.org:443
2.0snetworkCONNECT tcp://registry.npmjs.org:443
2.0snetworkCONNECT tcp://registry.npmjs.org:443
2.0sprocessexec /usr/local/bin/npm
2.0sprocessexited 243: npm error A complete log of this run can be found in: /tmp/ks-detonate-WrqKpk/later/home/.npm/_logs/2027-01-02T14_24_37_361Z-debug-0.log

Static findings

No findings across 384 lines in 4 files.

Cost to the agent

Instructions loaded
≈1,043 tok
1 file · 4 in bundle

Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.

Known vulnerabilities

Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.