BrowserSkill
Let AI agents use your real, logged-in browser without interrupting your work. CLI + extension for browser automation across any shell-capable AI agent.
Runssource: GitHubTypeScriptMITcommit f62e283cbb84
TypeScript, MIT licensed. The project labels itself: agent, browser use and dsh plugin.
BrowserSkill runs. An Argusic agent installed it in 14 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
The bsk CLI binary builds and runs, the daemon starts and responds to status/doctor, all 162 Rust unit tests pass, all 2341 extension unit tests pass, all 79 VOM tests pass, and the extension builds into dist/chrome-mv3/ without errors.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- Node.js 18 (v18.19.1) lacks `styleText` in `node:util`, which rolldown/vitest dependency requires2 minutes
- rolldown native bindings built for Node 18 were incompatible after switching to Node 221 minute
- vitest could not find `.wxt/tsconfig.json` needed by vite:oxc plugin1 minute
- Install time
- 14 minutes
- Cold machine to finish
- 17 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- cargo test --workspace --locked passed 162/162; pnpm ext:test passed 2341/2463 (122 skipped); pnpm vom:test passed 79/79; ./target/release/bsk --version returned 'bsk 0.3.1'; ./target/release/bsk status --json returned valid daemon JSON; bsk doctor reported all checks ok except 'extension connected' (expected no browser)
- Model tokens used
- 68,334
- Exact commit tested
- f62e283cbb84
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
test pid_alive_for_nonexistent_pid ... ok
test second_acquire_in_same_process_fails ... ok
test result: ok. 3 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s
Running tests/logs_cmd.rs (target/debug/deps/logs_cmd-0bcc42051cebcd95)
running 2 tests
test bsk_logs_handles_empty_home_gracefully ... ok
test daemon_writes_log_and_bsk_logs_prints_them ... ok
test result: ok. 2 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.59s
All integration tests pass. Let me compile the final summary.
tokens used
68,334
All integration tests pass. Let me compile the final summary.Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Recovered from all 3 errors without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed MIT, as reported by its host.
What did not, or is not known
- Took 14 minutes to install, slower than the median of the 51 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 52 agent projects Argusic has installed and timed, BrowserSkill was the 37th fastest to reach a running state, and 36 of 52 reached one at all.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/browserskill)Questions
- Does BrowserSkill run?
- Yes. BrowserSkill runs. Argusic installed and launched it on a clean machine in 14 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test BrowserSkill?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit f62e283cbb84. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test BrowserSkill?
- The run that produced this verdict cost $0.08: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does BrowserSkill take to install?
- 14 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does BrowserSkill need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing BrowserSkill?
- 3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does BrowserSkill compare with the alternatives?
- Of the 52 agent projects Argusic has installed and timed, BrowserSkill was the 37th fastest to reach a running state, and 36 of 52 reached one at all.
- Where is the evidence for BrowserSkill?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.