tld
Software architecture diagramming tool. Includes a modern easy to use Frontend + Backend + CLI to enable managing diagrams from the shell or in CI.
Runssource: GitHubhomepageTypeScriptApache-2.0commit a67274fc43f9
TypeScript, Apache-2.0 licensed. The project labels itself: agent skill, claude code plugin, diagram, diagramming as code and diagramming tool.
tld runs. An Argusic agent installed it in 25 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
tld builds into /tmp/tld, runs as a background web server on 127.0.0.1:18060 serving the frontend with HTTP 200, and all 61 Go test packages pass
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 binary not found in container; repo requires Go 1.26.26 minutes
- frontend build required Node >=20.19 but container had Node 18; vite 8 crashed on CustomEvent6 minutes
- go embed required frontend/dist which did not exist6 minutes
- npm install skipped @rolldown/binding-linux-x64-gnu optional native binding, vite build failed4 minutes
- Install time
- 25 minutes
- Cold machine to finish
- 9 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- go build -o /tmp/tld ./cmd/tld succeeded; /tmp/tld version printed tld version 2.3.5; /tmp/tld serve --host 127.0.0.1 --port 18060 --data-dir /tmp/tld-test-data started background server; curl -s -o /dev/null -w %{http_code} http://127.0.0.1:18060/ returned 200 and served frontend HTML; go test ./... passed: 61 packages ok, 0 FAIL
- Model tokens used
- 159,145
- Exact commit tested
- a67274fc43f9
- 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.
Done. Summary of the run: **Installed** - Go 1.26.2 (user-level, `~/src/go`) — container had no Go toolchain. - Node 20.19.0 (user-level, `~/src/node-v20.19.0-linux-x64`) — Vite 8 requires Node ≥ 20.19; the co… - `@rolldown/[email protected]` — the platform native binding was skipped by `npm install… - Built the frontend (`npm run build:app`) so the Go `//go:embed frontend/dist` would resolve, then… **Verified** - `tld version` → `tld version 2.3.5` - `tld serve --host 127.0.0.1 --port 18060 --data-dir /tmp/tld-test-data` → background server, `cur… - `go test ./...` → 61 packages `ok`, 0 failures (includes `internal/watch` at 60s) - `tld stop` shut the server down cleanly No third-party keys were required for local serve or tests; no system packages were installed.
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 4 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 Apache-2.0, as reported by its host.
What did not, or is not known
- Took 25 minutes to install, slower than the median of the 13 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 14 agent-skill projects Argusic has installed and timed, tld was the 13th fastest to reach a running state, and 12 of 14 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.
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)
agent-skillclaude-code-plugindiagramdiagramming-as-codediagramming-tool
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/tld)Questions
- Does tld run?
- Yes. tld runs. Argusic installed and launched it on a clean machine in 25 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test tld?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit a67274fc43f9. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test tld?
- The run that produced this verdict cost $0.07: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does tld take to install?
- 25 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 tld need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing tld?
- 4 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does tld compare with the alternatives?
- Of the 14 agent-skill projects Argusic has installed and timed, tld was the 13th fastest to reach a running state, and 12 of 14 reached one at all.
- Where is the evidence for tld?
- 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.