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 12 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
PHP 8.4.26 and Composer 2.10.3 are installed locally, all 38 dependencies are in vendor/, the Mink test suite passes 520 tests with 1165 assertions, composer.json validates, phpstan reports no errors, and a stub-driver script using the Mink library successfully found the Downloads link with href /download.
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.
- Composer could not extract zip dist packages: no unzip/7z binary and PHP zip extension unloadable (libzip.so.4 missing)4 minutes
- No PHP runtime installed in container3 minutes
- PHP extensions missing (phar, iconv, mbstring, dom, xml, tokenizer, ctype, curl)3 minutes
- PHPStan crashed with 128M default memory limit1 minute
- PHP zip extension could not load (libzip.so.4 shared library absent; no root to install libzip)
- Install time
- 12 minutes
- Cold machine to finish
- 12 minutes
- Errors hit and fixed
- 5 hit, 5 fixed with no human help
- How the result was proved
- php8.4 vendor/bin/phpunit -c phpunit.xml.dist returned 'OK (520 tests, 1165 assertions)'; composer.phar validate --strict --no-check-lock returned './composer.json is valid'; vendor/bin/phpstan analyze --memory-limit 512M returned '[OK] No errors'; PHP script using Behat\Mink\Mink with stub driver returned 'Link href: /download', 'Content length: 83'
- Model tokens used
- 842,249
- 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.
- **Fixed**: Composer zip extraction (no unzip binary, PHP zip ext broken by missing libzip.so.4) v… - **Verified**: `phpunit` → `OK (520 tests, 1165 assertions)`; `composer validate` → valid; `phpsta… - Repo working tree restored to clean (vendor/, composer.phar, composer.lock are gitignored). tokens used 842,249 All verification complete. Let me compile the final report. **Work Summary:** - **Environment**: Container had no PHP/Composer. Installed pre-built static PHP 8.4.26 (shivammath… - **Required extensions** (phar, iconv, mbstring, dom, xml, xmlwriter, tokenizer, ctype, curl) load… - **Fixed**: Composer zip extraction (no unzip binary, PHP zip ext broken by missing libzip.so.4) v… - **Verified**: `phpunit` → `OK (520 tests, 1165 assertions)`; `composer validate` → valid; `phpsta… - Repo working tree restored to clean (vendor/, composer.phar, composer.lock are gitignored).
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.
- Installed in 12 minutes.
- Recovered from all 5 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
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
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 12 minutes, hitting 5 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. One attempt is 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.19: 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?
- 12 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?
- 5 things broke in the recorded run, and 5 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for Mink?
- 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.