agents
Multi-harness agentic plugin marketplace for Claude Code, Codex, Cursor, OpenCode, GitHub Copilot, Google Antigravity, and Pi
Runssource: GitHubhomepagePythonMITcommit 4236bb91f839
Python, MIT licensed. The project labels itself: agent skills, agentic ai, ai agents, anthropic, antigravity, claude, claude code and claude code marketplace.
agents runs. An Argusic agent installed it in 2 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
uv sync installs all deps for both projects; pytest suite passes 619/621; all 6 harness generators emit artifacts; codex doctor reports 20/20 checks ok; structural validation passes across 6 harnesses with strict mode
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 98.7 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.
- uv not installed1 minute
- codex doctor failed due to TERM=dumb in test env1 minute
- npx skills requires Node.js >=22, container has v18.19.11 minute
- Install time
- 2 minutes
- Cold machine to finish
- 11 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- pytest: 619 passed, 2 skipped; codex doctor: 20/20 ok, overall=ok; validate_generated: OK across 6 harnesses; all 6 generators produce artifacts; plugin-eval scores a skill at 72.6/100
- Model tokens used
- 74,222
- Exact commit tested
- 4236bb91f839
- 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.
- `make generate HARNESS=codex --all --prune` → **908 files written**
- All 6 harness generators succeed: codex (908), antigravity (824), opencode (733), pi (732), copil…
- Smoke tests: 4 passed, 10 skipped (CLIs not on PATH), 1 pre-existing failure (`npx skills@latest`…
**Errors encountered and fixed:**
1. `uv: not found` → installed uv via astral.sh installer (~1 min)
2. `codex doctor` failed with `TERM=dumb` → patched test to pass `TERM=xterm-256color` env var
exec
/bin/sh -lc "echo '{\"install_succeeded\": true, \"launch_succeeded\": true, \"install_minutes\": 2…
succeeded in 0ms:
{"install_succeeded": true, "launch_succeeded": true, "install_minutes": 2, "errors": [{"msg": "uv …
tokens used
74,222Replay 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 2 minutes, faster than the median of the 8 comparable projects Argusic has measured.
- Recovered from all 3 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 MIT, as reported by its host.
- Measured 3 times, so the result is not a one-off.
Of the 9 agent-skills projects Argusic has installed and timed, agents was the 5th 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.
- A quick evaluation: it was running 2 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
Topics (from GitHub)
agent-skillsagentic-aiai-agentsanthropicantigravityclaudeclaude-codeclaude-code-marketplaceclaude-code-pluginclaude-skillscodexcoding-agentscursorcursor-rulesgithub-copilotmcpmulti-agentopencodepi-coding-agentsubagents
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/agents)Questions
- Does agents run?
- Yes. agents runs. Argusic installed and launched it on a clean machine in 2 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test agents?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 4236bb91f839. 3 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test agents?
- The run that produced this verdict cost $0.05: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does agents take to install?
- 2 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 agents need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing agents?
- 3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does agents compare with the alternatives?
- Of the 9 agent-skills projects Argusic has installed and timed, agents was the 5th fastest to reach a running state, and 8 of 9 reached one at all.
- Where is the evidence for agents?
- All 3 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.