Yes. tagref runs. Argusic installed and launched it on a clean machine in 8 minutes, hitting 1 error on the way, and recorded the session.

How did Argusic test tagref?

On a fresh, disposable machine, with every command recorded and the repository pinned at commit 4894b87986ca. One attempt is recorded, and the full method is on the methodology page.

What did it cost to test tagref?

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 tagref take to install?

8 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 tagref need a GPU?

Not to start. Argusic reached a running state on a machine with no GPU.

What goes wrong when installing tagref?

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 tagref?

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.

tagref

Manage cross-references in your code.

Runssource: GitHubRustMITcommit 4894b87986ca

Rust, MIT licensed. The project labels itself: continuous integration, cross reference, cross references, cross referencing and linter.

tagref runs. An Argusic agent installed it in 8 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Tagref 1.14.0 installed and verified: prebuilt binary and source build both run, its 29-test suite passes, and it validates real tag/group/reference fixtures with correct exit codes on both passing and failing cases.
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

verdict: Runs
Argusic Score: 100 / 100
cost of the verifying run: $0.01 (measured)
recorded runs: 1
last tested: 2026-10-28
stars: 242
forks: 9
open issues: 2
watchers: 2
size: 1 MB
created: 2018-05-22
last push: 2026-10-25

Subject data from GitHub, linked at the top of this page, refreshed 2026-10-28. 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.

Time lost to each failure while testing tagref, drawn from the recorded run — Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

Official install.sh failed on first run: target dir missing, mv failed, then the script hit a sudo branch needing a tty (cannot open /dev/tty) and exited with "Unable to install the binary"2 minutes

Install time: 8 minutes
Cold machine to finish: 2 minutes
Errors hit and fixed: 1 hit, 1 fixed with no human help
How the result was proved: install.sh printed 'tagref 1.14.0'; cargo test --locked exited 0 with 29 passed, 0 failed; tagref on a scratch repo exited 0 printing '1 tag, 0 group members, 1 reference, 1 file reference, and 1 directory reference validated in 3 files', a dangling [ref:no_such_tag] exited 1, and cargo run self-checking the repo exited 0 printing '11 tags, 14 group members, 13 references, 11 file references, and 5 directory references validated in 31 files'
Model tokens used: 58,173
Exact commit tested: 4894b87986ca
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 1, run 2026-10-28, the attempt that decided the verdict above. 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.

Done. Tagref (Rust CLI, v1.14.0) installed and fully verified from install to end-to-end behavior —…
- `install.sh` → `tagref 1.14.0` printed (one install error fixed: script exited on missing `~/.loc…
- Real fixture: `tagref` exited 0 with `1 tag, 0 group members, 1 reference, 1 file reference, and …
- Negative test: dangling `[ref:no_such_tag]` → exit 1.
- Rust 1.99.1 installed via rustup (no root); `cargo build --locked` exit 0; `NO_COLOR=true cargo t…
- Repo self-check `cargo run` → `11 tags, 14 group members, 13 references, 11 file references, and …
exec
/bin/sh -lc "printf '%s' '{\"msg\": \"Official install.sh failed on first run: target dir missing, …
 succeeded in 0ms:
{"msg": "Official install.sh failed on first run: target dir missing, mv failed, then the script hi…
tokens used
58,173

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 8 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.

What did not, or is not known

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 8 minutes after the clone.

Run history

tested by	attempt	outcome	score	cost USD	when
Argusic Runner	1/3	Runs	100.00	0.01	2026-10-28 10:21 UTC

Topics (from GitHub)

continuous-integration cross-reference cross-references cross-referencing linter

Embed the badge

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

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

Questions

Does tagref run?: Yes. tagref runs. Argusic installed and launched it on a clean machine in 8 minutes, hitting 1 error on the way, and recorded the session.
How did Argusic test tagref?: On a fresh, disposable machine, with every command recorded and the repository pinned at commit 4894b87986ca. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test tagref?: 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 tagref take to install?: 8 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 tagref need a GPU?: Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing tagref?: 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 tagref?: 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.