gojekyll
A fast Go implementation of the Jekyll blogging engine
Runssource: GitHubGoMITcommit e4135dfb4376
Go, MIT licensed. The project labels itself: blog engine, cli, golang, jekyll, liquid and static site generator.
gojekyll runs. An Argusic agent installed it in 4 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
The gojekyll binary builds and runs locally: the full test suite passes (15 packages, 406 tests, 0 failures), real sites build (testsite: 3 files, example: 20 files) with compiled SCSS to valid CSS, and gojekyll serve answered HTTP 200 with rendered HTML on / and /2024/01/01/test-post.html.
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.
- go: not found — no Go toolchain installed2 minutes
- sass: executable file not found in $PATH — 2 filter tests failed (sassify/scssify)2 minutes
- Install time
- 4 minutes
- Cold machine to finish
- 5 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- How the result was proved
- go test -count=1 -v ./... exited 0: all 15 packages ok, 138 top-level + 268 nested tests passed, 0 failed; gojekyll build -s testsite wrote 3 files; gojekyll serve answered curl HTTP 200 on / and on the rendered post page
- Model tokens used
- 65,480
- Exact commit tested
- e4135dfb4376
- 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.
- Module cache and build artifacts live in `/work/repo/.gopath` and `/work/repo/gojekyll` (both git… **Errors hit and fixed:** 1. `go: not found` — resolved by local Go toolchain install. 2. `sass: executable file not found in $PATH` failing 2 tests (`TestFilters/36`, `TestFilters/37`) … **Verification (all observed directly):** - `go build ./...` and `go build -o gojekyll .` both exited 0. - `./gojekyll --version` printed `gojekyll version develop`; `./gojekyll help` printed full usage. - `go test -count=1 -v ./...`: all 15 packages `ok`, 138 top-level `--- PASS` + 268 nested `--- PAS… - `gojekyll build -s testsite` wrote 3 files (exit 0); the built `index.html` contained real render… - `gojekyll build -s example` wrote 20 files (exit 0); the `jekyll-github-metadata` plugin logged o… - `gojekyll serve -s testsite --host 127.0.0.1 --port 4599`: server started; `curl` returned **200*… Test depth is **tier1_real** — no mocks needed; everything ran against real, local behavior.
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 4 minutes, faster than the median of the 4 comparable projects Argusic has measured.
- Recovered from all 2 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.
Of the 5 blog-engine projects Argusic has installed and timed, gojekyll was the 3rd fastest to reach a running state, and 5 of 5 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 4 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/gojekyll)Questions
- Does gojekyll run?
- Yes. gojekyll runs. Argusic installed and launched it on a clean machine in 4 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test gojekyll?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit e4135dfb4376. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test gojekyll?
- The run that produced this verdict cost $0.03: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does gojekyll take to install?
- 4 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 gojekyll need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing gojekyll?
- 2 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does gojekyll compare with the alternatives?
- Of the 5 blog-engine projects Argusic has installed and timed, gojekyll was the 3rd fastest to reach a running state, and 5 of 5 reached one at all.
- Where is the evidence for gojekyll?
- 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.