archify
Agent skill for beautiful, verifiable architecture, workflow, sequence, data-flow, and lifecycle diagrams, self-contained HTML with motion and crisp export.
Runssource: GitHubhomepageJavaScriptMITcommit 5de7275fe87a
JavaScript, MIT licensed. The project labels itself: agent skills, architecture as code, architecture diagram, claude skill, code visualization, codex, coding agents and data flow diagram.
archify runs. An Argusic agent installed it in 34 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Archify v2.16.0 is fully installed and functional: 'npm install' succeeded in the archify/ directory, all 5 renderers (architecture, workflow, sequence, dataflow, lifecycle) produce correct output, the CLI tool reports 'Archify is ready' via doctor, and 981/1013 automated tests 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.
- Test 151: spawnSync unzip ENOENT — unzip command not found in container
- Install time
- 34 minutes
- Cold machine to finish
- 18 minutes
- Errors hit and fixed
- 1 hit, 1 fixed with no human help
- Exact commit tested
- 5de7275fe87a
- Container image
- sha256:33ceb71981b6
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.
- How the result was proved
- runs before 2026-09-07 did not record the command used to check the result
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Model tokens used
- not recorded for this run
- 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.
Test summary: 981 passed, 1 failed, 31 skipped, 0 cancelled. The single failure (test 151) is 'spaw…
exec
/bin/sh -lc 'echo "Install started at:" && date -u' in /work/repo
succeeded in 0ms:
Install started at:
Tue Sep 1 10:55:09 UTC 2026
Now I'll compute the elapsed time - the whole process took approximately 34 minutes (considering th…
ARGUSIC_RESULT: {"install_succeeded":true,"launch_succeeded":true,"install_minutes":34,"errors":[{"…
tokens used
34,791
Now I'll compute the elapsed time - the whole process took approximately 34 minutes (considering th…
ARGUSIC_RESULT: {"install_succeeded":true,"launch_succeeded":true,"install_minutes":34,"errors":[{"…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 34 minutes to install, slower than the median of the 8 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 9 agent-skills projects Argusic has installed and timed, archify was the 9th fastest to reach a running state, and 8 of 9 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-skillsarchitecture-as-codearchitecture-diagramclaude-skillcode-visualizationcodexcoding-agentsdata-flow-diagramdeepseek-harnessdeveloper-toolsdiagram-as-codediagramsdiagrams-as-codedsh-pluginmermaid-alternativeopencodesequence-diagramsoftware-architecturesystem-designtext-to-diagram
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/archify)Questions
- Does archify run?
- Yes. archify runs. Argusic installed and launched it on a clean machine in 34 minutes, hitting 1 error on the way, and recorded the session.
- How did Argusic test archify?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 5de7275fe87a. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test archify?
- The run that produced this verdict cost $0.04: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does archify take to install?
- 34 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 archify need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing archify?
- 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 archify compare with the alternatives?
- Of the 9 agent-skills projects Argusic has installed and timed, archify was the 9th fastest to reach a running state, and 8 of 9 reached one at all.
- Where is the evidence for archify?
- 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.