cheat.sh
the only cheat sheet you need
Runssource: GitHubhomepagePythonMITcommit 031a5d3887f0
Python, MIT licensed. The project labels itself: cheatsheet, cli, command line, curl, documentation, examples, hacktoberfest2021 and help.
cheat.sh runs. An Argusic agent installed it in 18 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
cheat.sh HTTP server is running on port 8002 with no-cache mode, serving cheat sheets from 6 fetched upstream repositories across all configured adapters (tldr, cheat, cheat.sheets, learnxiny, rosetta, late.nz).
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 97.3 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.
- PyICU cannot be built: no ICU development headers (libicu-dev, icu-devtools) on system, no root5 minutes
- Install time
- 18 minutes
- Cold machine to finish
- 16 minutes
- Errors hit and fixed
- 1 hit, 1 fixed with no human help
- How the result was proved
- Server started with CHEATSH_CACHE_TYPE=none; curl tested endpoints /:help, /, /tar, /ls, /python/:list, /python/:learn, /python/rosetta/:list, /az, all returned HTTP 200 with real ANSI content (2508-38705 bytes)
- Model tokens used
- 100,553
- Exact commit tested
- 031a5d3887f0
- 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
Watch the session
The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.
A recording of attempt 2, run . The verdict above comes from a different attempt, so read this as one session and not as the current result. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
All systems verified. Here's the final report: **Installation**: Created a Python virtualenv and installed all dependencies except PyICU (requires… **Upstream data**: Fetched 6 repositories (cheat, tldr, learnxinyminutes, rosetta, cheat.sheets, la… **Server**: Starts on port 8002 using gevent. All endpoints return HTTP 200 with real content: - `/:help` → 2508 bytes - `/` → 25502 bytes - `/tar` → 9101 bytes (ANSII-formatted cheat sheet) - `/ls` → 4043 bytes - `/python/:list` → 85 bytes - `/python/rosetta/:list` → 38705 bytes - `/az` → 13269 bytes **Tests**: `py.test` on `lib/cheat_wrapper_test.py` passes (1/1). The `tests/run-tests.sh` suite ha…
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 18 minutes.
- Recovered from all 1 error 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 3 times, so the result is not a one-off.
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)
cheatsheetclicommand-linecurldocumentationexampleshacktoberfest2021helpterminaltldr
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/cheat-sh)Questions
- Does cheat.sh run?
- Yes. cheat.sh runs. Argusic installed and launched it on a clean machine in 18 minutes, hitting 1 error on the way, and recorded the session.
- How did Argusic test cheat.sh?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 031a5d3887f0. 3 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test cheat.sh?
- 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 cheat.sh take to install?
- 18 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 cheat.sh need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing cheat.sh?
- 1 thing broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for cheat.sh?
- All 3 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.