Cowart
Runssource: GitHubJavaScriptMITcommit 43fc8882daf2
JavaScript, MIT licensed.
Cowart runs. An Argusic agent installed it in 1.4 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
npm install completes, all 8 quality checks pass, the MCP server initializes and lists 14 tools and 1 resource, the self-contained widget HTML is valid, and the cold-install probe confirms the plugin works with zero runtime dependencies.
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 96 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.
- crypto is not defined in posthog-analytics.mjs on Node.js 18 (ESM global not available)0.3 minutes
- Install time
- 1 minutes
- Cold machine to finish
- 4 minutes
- Errors hit and fixed
- 1 hit, 1 fixed with no human help
- How the result was proved
- `npm run quality` exited 0: all 8 sub-steps passed. `echo '{...initialize...}' | timeout 5 node scripts/start-mcp.mjs` returned a valid MCP initialize result with protocolVersion 2024-11-05, serverInfo name 'cowart' version '0.1.28'. `probe-mcp.mjs --tools-only` and `probe-mcp.mjs` both exited 0 confirming tools and widget available. Cold-install probe verified no node_modules or npm calls in the sandboxed plugin directory.
- Model tokens used
- 82,743
- Exact commit tested
- 43fc8882daf2
- 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 . The verdict above comes from a different attempt, so read this as one session and not as the current result. 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.
/bin/sh -lc 'cd /work/repo && git log --oneline -1 2>/dev/null && date -u +%s' in /work/repo succeeded in 0ms: 43fc888 docs: link Token Arena sponsor section to in-repo demo video 1794005033 exec /bin/sh -lc 'echo "install start: 1794004950"; echo "now: 1794005033"; echo "diff: $((1794005033 - … succeeded in 0ms: install start: 1794004950 now: 1794005033 diff: 83 seconds tokens used 82,743
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 1.4 minutes, faster than the median of the 14 comparable projects Argusic has measured.
- 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.
- Measured 2 times, so the result is not a one-off.
Of the 15 JavaScript projects Argusic has installed and timed, Cowart was the 6th fastest to reach a running state, and 10 of 15 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 1.4 minutes after the clone.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Runs | 100.00 | 0.04 | |
| Argusic Runner | 1/3 | Runs with mocks | 92.00 | 0.07 |
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/cowart)Questions
- Does Cowart run?
- Yes. Cowart runs. Argusic installed and launched it on a clean machine in 1 minutes, hitting 1 error on the way, and recorded the session.
- How did Argusic test Cowart?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 43fc8882daf2. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test Cowart?
- 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 Cowart take to install?
- 1.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 Cowart need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing Cowart?
- 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 Cowart compare with the alternatives?
- Of the 15 JavaScript projects Argusic has installed and timed, Cowart was the 6th fastest to reach a running state, and 10 of 15 reached one at all.
- Where is the evidence for Cowart?
- All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.