dotfiles
Get started with your own dotfiles.
Could not verifysource: GitHubhomepageShellMITcommit 0d7a71d73305
Shell, MIT licensed. The project labels itself: backup, brew, dotfiles, homebrew, macos, oh my zsh, shell and zsh.
Argusic could not get dotfiles running. An Argusic agent installed it in 5 minutes and hit 2 errors on a clean machine with no GPU, and the whole session was recorded.
All 13 dotfiles are present and pass syntax validation. Oh My Zsh is installed with the artisan plugin and minimal theme. Shell aliases (46 total), Zsh theme components (6), and artisan plugin functions (5) all load correctly. The .zshrc correctly resolves DOTFILES, ZSH_CUSTOM, plugins and theme settings. macOS-specific files (Brewfile, .macos, fresh.sh, clone.sh) are present but require macOS/Homebrew to execute.
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 45 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.
- Zsh native modules (zle.so, parameter.so) missing from bundled zsh — oh-my-zsh shell integration degraded5 minutes
- SSH unavailable for git submodule — used HTTPS fallback for plugins/artisan1 minute
- Install time
- 5 minutes
- Cold machine to finish
- 6 minutes
- Errors hit and fixed
- 2 hit, 1 fixed with no human help
- How the result was proved
- aliases.zsh sourced: 46 aliases defined (shrug, gs, dotfiles all resolved). minimal.zsh-theme loaded: 6 prompt components (mnml_status, mnml_keymap, mnml_cwd, mnml_git, mnml_err, mnml_uhp) all available. artisan.plugin.zsh loaded: 5 functions (artisan, _artisan_find, _artisan_get_command_list, _artisan_add_completion, _docker_compose_cmd) registered. .zshrc symlinked: DOTFILES=/home/runner/.dotfiles, ZSH_CUSTOM=$DOTFILES, plugins=(artisan git) resolved.
- Model tokens used
- 80,846
- Exact commit tested
- 0d7a71d73305
- 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
- Whether it works at all
- this run verified nothing, so this page makes no claim either way
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
- **6 theme components** from `minimal.zsh-theme` all available - **All 13 config files** present and pass syntax validation Limitations inherent to this environment: the bundled zsh lacks native shared modules (no `zle.so` … tokens used 80,846 The verification is complete. The repository is `driesvints/dotfiles` — a personal macOS dotfiles c… - **Oh My Zsh** installed and configured - **Artisan plugin** populated via HTTPS and its 5 functions load correctly - **46 aliases** all resolve from `aliases.zsh` - **6 theme components** from `minimal.zsh-theme` all available - **All 13 config files** present and pass syntax validation Limitations inherent to this environment: the bundled zsh lacks native shared modules (no `zle.so` …
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 5 minutes, faster than the median of the 10 comparable projects Argusic has measured.
- 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.
- Hit 2 errors during setup, 1 of which were not solved.
Of the 11 backup projects Argusic has installed and timed, dotfiles was the 3rd fastest to reach a running state, and 8 of 11 reached one at all.
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
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Unverified | 70.00 | 0.01 | |
| Argusic Runner | 1/3 | Did not run | 20.00 | 0.01 |
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/dotfiles)Questions
- Does dotfiles run?
- Argusic could not verify that dotfiles runs. Argusic installed and launched it on a clean machine in 5 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test dotfiles?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 0d7a71d73305. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test dotfiles?
- The run that produced this verdict cost $0.01: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does dotfiles take to install?
- 5 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 dotfiles need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing dotfiles?
- 2 things broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does dotfiles compare with the alternatives?
- Of the 11 backup projects Argusic has installed and timed, dotfiles was the 3rd fastest to reach a running state, and 8 of 11 reached one at all.
- Where is the evidence for dotfiles?
- 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.