Codex-Dream-Skin
Codex Dream Skin
Could not verifysource: GitHubJavaScriptMITcommit 34335d27d543
JavaScript, MIT licensed.
Argusic could not get Codex-Dream-Skin running. An Argusic agent installed it in 0 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.
The repository's cross-platform Node.js test suite passes at v1.5.18: 151 tests pass, 0 fail, 3 expected platform skips; shared runtime assets are synchronised between macOS and Windows; no install-time or runtime 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 40 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page. 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.
- Install time
- under a minute
- Cold machine to finish
- 6 minutes
- Errors hit and fixed
- 0 hit, 0 fixed with no human help
- How the result was proved
- node --test 35 test files across macos/tests/, windows/tests/, and tools/, 154 total tests, 151 pass, 0 fail, 3 skip. tools/sync-runtime-assets.mjs: 16 files synced, all cross-platform payloads identical. bash -n validation on all shell scripts clean. git status: clean tree at 34335d27 (v1.5.18).
- Model tokens used
- 303,453
- Exact commit tested
- 34335d27d543
- 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 'cd /work/repo && node --test macos/tests/restart-cancellation.test.mjs 2>&1 | grep -E … succeeded in 1739ms: # tests 12 # pass 11 # fail 0 # skipped 1 All tests pass with no errors. Here is the comprehensive result: **154 tests** (151 pass, 0 fail, 3 skip) across the full cross-platform suite. The 3 skipped tests … tokens used 303,453 All tests pass with no errors. Here is the comprehensive result: **154 tests** (151 pass, 0 fail, 3 skip) across the full cross-platform suite. The 3 skipped tests …
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
- Installed in 0 minutes.
- Nothing broke on the way: zero errors between clone and running.
- 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
- An agent with no time limit did not get it running.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Did not run | 50.00 | 0.04 | |
| Argusic Runner | 1/3 | Did not run | 30.00 | 0.03 |
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/codex-dream-skin)Questions
- Does Codex-Dream-Skin run?
- Argusic could not verify that Codex-Dream-Skin runs. Argusic installed and launched it on a clean machine in 0 minutes, hitting 0 errors on the way, and recorded the session.
- How did Argusic test Codex-Dream-Skin?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 34335d27d543. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test Codex-Dream-Skin?
- The run that produced this verdict cost $0.04: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does Codex-Dream-Skin take to install?
- 0 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 Codex-Dream-Skin need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing Codex-Dream-Skin?
- Nothing did, in the recorded run: zero errors between clone and running.
- Where is the evidence for Codex-Dream-Skin?
- 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.