Mink
PHP web browser emulator abstraction
Runssource: GitHubhomepagePHPMITcommit 1efa65994430
PHP, MIT licensed. The project labels itself: browser automation, mink and php.
Mink runs. An Argusic agent installed it in 6 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
PHP 8.3.6 extracted from Ubuntu 24.04 debs, Composer 2.11.2 installed, 39 PHP dependencies installed, phpunit 9.6.39 runs and passes all 520 tests with 1165 assertions
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.
- No PHP interpreter in container2 minutes
- Composer install failed: ext-dom, ext-xml, ext-xmlwriter, ext-tokenizer required2 minutes
- PHAR and ICONV extensions missing preventing Composer install1 minute
- Install time
- 6 minutes
- Cold machine to finish
- 5 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- phpunit exited 0, 520 passed, 1165 assertions
- Model tokens used
- 79,724
- Exact commit tested
- 1efa65994430
- 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.
/bin/sh -lc 'date -u +%s' in /work/repo
succeeded in 0ms:
1794662484
exec
/bin/sh -lc "echo '{\"install_succeeded\": true, \"launch_succeeded\": true, \"install_minutes\": 6…
succeeded in 0ms:
{"install_succeeded": true, "launch_succeeded": true, "install_minutes": 6, "errors": [{"msg": "No …
exec
/bin/sh -lc "echo 'ARGUSIC_RESULT:{\"install_succeeded\":true,\"launch_succeeded\":true,\"install_m…
succeeded in 0ms:
tokens used
79,724Replay 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.
- Measured 2 times, so the result is not a one-off.
What did not, or is not known
- Took 6 minutes to install, slower than the median of the 14 comparable projects Argusic has measured.
Of the 15 browser-automation projects Argusic has installed and timed, Mink was the 12th fastest to reach a running state, and 13 of 15 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.
- A quick evaluation: it was running 6 minutes after the clone.
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/mink)Questions
- Does Mink run?
- Yes. Mink runs. Argusic installed and launched it on a clean machine in 6 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test Mink?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 1efa65994430. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test Mink?
- The run that produced this verdict cost $0.07: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does Mink take to install?
- 6 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 Mink need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing Mink?
- 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 Mink compare with the alternatives?
- Of the 15 browser-automation projects Argusic has installed and timed, Mink was the 12th fastest to reach a running state, and 13 of 15 reached one at all.
- Where is the evidence for Mink?
- All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.