goread
cli epub reader written in Go
Runssource: GitHubGoMITcommit 7c25bdbb120d
Go, MIT licensed. The project labels itself: cli, cli app, epub, epub reader, go, gocli and golang.
goread runs. An Argusic agent installed it in 3 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
GoRead binary compiled and runs correctly, all 12 unit tests pass, help and version flags work, no history file present as expected for a fresh install.
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.
- fmt.Println with raw string literal has redundant trailing newline in cmd/goread/utils.go:820.5 minutes
- Install time
- 3 minutes
- Cold machine to finish
- 3 minutes
- Errors hit and fixed
- 1 hit, 1 fixed with no human help
- How the result was proved
- make build exits 0, ./goread --help prints usage, ./goread -v prints version 0.1.0, go test ./... exits 0 with 12/12 passed
- Model tokens used
- 112,674
- Exact commit tested
- 7c25bdbb120d
- 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.
Here's the final report: **Install**: Downloaded Go 1.23.2 tarball and extracted it to `/home/runner/go/bin/go`, ran `make b… **Error found and fixed**: `cmd/goread/utils.go:82` had `fmt.Println` with a raw string literal end… **Build & tests**: `go build` exits 0. `go test ./...` exits 0 — 12 tests pass across 2 packages (`… **Binary verification**: `./goread --help` prints usage info; `./goread -v` prints version 0.1.0 an… tokens used 112,674 Here's the final report: **Install**: Downloaded Go 1.23.2 tarball and extracted it to `/home/runner/go/bin/go`, ran `make b… **Error found and fixed**: `cmd/goread/utils.go:82` had `fmt.Println` with a raw string literal end… **Build & tests**: `go build` exits 0. `go test ./...` exits 0 — 12 tests pass across 2 packages (`… **Binary verification**: `./goread --help` prints usage info; `./goread -v` prints version 0.1.0 an…
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.
- 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.
What did not, or is not known
- Took 3 minutes to install, slower than the median of the 127 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 128 cli projects Argusic has installed and timed, goread was the 65th fastest to reach a running state, and 117 of 128 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 3 minutes after the clone.
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)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/goread)Questions
- Does goread run?
- Yes. goread runs. Argusic installed and launched it on a clean machine in 3 minutes, hitting 1 error on the way, and recorded the session.
- How did Argusic test goread?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 7c25bdbb120d. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test goread?
- 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 goread take to install?
- 3 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 goread need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing goread?
- 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.
- How does goread compare with the alternatives?
- Of the 128 cli projects Argusic has installed and timed, goread was the 65th fastest to reach a running state, and 117 of 128 reached one at all.
- Where is the evidence for goread?
- 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.