typikon

Typikon lets you use markdown to write your online books.

Runssource: GitHubhomepageRustApache-2.0commit d81a1a9e66e6

Rust, Apache-2.0 licensed. The project labels itself: book, books, bootstrap5, dcos, docs, full text search, html and hugo.

typikon runs. An Argusic agent installed it in 5 minutes and hit 1 error on a clean machine with no GPU, and the whole session was recorded.

Typikon builds from source, passes 7/8 unit tests, compiles book markdown to HTML via 'cargo run -- build', and serves the output via HTTP on port 2478 via 'cargo run -- serve' responding with 200.

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 80 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs
Argusic Score
80 / 100
cost of the verifying run
$0.06 (measured)
recorded runs
1
last tested
stars
282
forks
7
open issues
2
watchers
2
size
18 MB
created
last push

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.

  • test_live_server hangs indefinitely because handle_watch_command() starts a blocking file-watcher loop
Install time
5 minutes
Cold machine to finish
10 minutes
Errors hit and fixed
1 hit, 0 fixed with no human help
How the result was proved
cargo test --test lib (excluding live_server_test) passed 7/7; cargo run -- build generated docs/index.html; cargo run -- serve returned HTTP 200 on localhost:2478
Model tokens used
328,645
Exact commit tested
d81a1a9e66e6
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.

- **Install**: `cargo build` succeeded after installing Rust via rustup. No code changes were neede…
- **Tests**: 7 of 8 tests pass. The 8th test (`test_live_server` in `tests/book/live_server_test.rs…
- **CLI**: `cargo run -- build` successfully generates HTML from the book markdown files into `docs…
- **Errors**: The only error is that the `test_live_server` test is a blocking watch command that n…
2026-10-26T13:26:01.294900Z ERROR codex_core::session: failed to record rollout items: thread 01a17…
tokens used
328,645
Now let me compile the final report. Here's the summary:
- **Install**: `cargo build` succeeded after installing Rust via rustup. No code changes were neede…
- **Tests**: 7 of 8 tests pass. The 8th test (`test_live_server` in `tests/book/live_server_test.rs…
- **CLI**: `cargo run -- build` successfully generates HTML from the book markdown files into `docs…
- **Errors**: The only error is that the `test_live_server` test is a blocking watch command that n…

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 5 minutes.
  • Ran without a GPU, so it does not need one to start.
  • Licensed Apache-2.0, as reported by its host.

What did not, or is not known

  • Hit 1 error during setup, 1 of which were not solved.
  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

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 5 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

tested byattemptoutcomescorecost USDwhen
Argusic Runner1/3Runs80.000.06

Topics (from GitHub)

bookbooksbootstrap5dcosdocsfull-text-searchhtmlhugojsmarkdownmarkdown-to-htmlmdbookmkdocsonlinerustrust-lang

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/typikon.svg)](https://argusic.com/subject/typikon)

Questions

Does typikon run?
Yes. typikon runs. Argusic installed and launched it on a clean machine in 5 minutes, hitting 1 error on the way, and recorded the session.
How did Argusic test typikon?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit d81a1a9e66e6. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test typikon?
The run that produced this verdict cost $0.06: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does typikon 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 typikon need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing typikon?
1 thing broke in the recorded run. Each one, and the time it cost, is listed on this page.
Where is the evidence for typikon?
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.

Discussion