agnix
The missing linter and lsp for AI coding assistants. Validate CLAUDE.md, AGENTS.md, SKILL.md, hooks, MCP. Plugin for all major IDEs included, with autofixes.
Runssource: GitHubRustApache-2.0commit e557022f0943
Rust, Apache-2.0 licensed. The project labels itself: agent, ai, ai agents, ai coding assistant, claude, cli, code quality and codex.
agnix runs. An Argusic agent installed it in 22.8 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
agnix 0.52.2 installed and working from both npm (user dir) and cargo source build; 4700+ tests passing across all 6 workspace crates; binary validates agent configs and produces text, JSON, SARIF, and GitHub annotations output formats with i18n support.
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.
- Rust toolchain not found (no rustc/cargo)16.6 minutes
- kiro_fixture_inventory test baseline drift: VER-001 info added 1 extra diagnostic per kiro-fix family2 minutes
- npm install -g failed due to EACCES on /usr/local/lib/node_modules1 minute
- pip install failed due to externally-managed-environment0.2 minutes
- Install time
- 23 minutes
- Cold machine to finish
- 20 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- cargo test passed 4700+ tests across all workspace crates; npm installed binary ran agnix --version returned 0.52.2; agnix tests/fixtures/skills found 1 error, 1 warning; agnix --format json tests/fixtures/kiro-powers returned valid JSON with 5 diagnostics; release binary built and tested
- Model tokens used
- 183,762
- Exact commit tested
- e557022f0943
- 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.
test result: ok. 37 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.41s test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s test result: ok. 47 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s test result: ok. 4 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.06s test result: ok. 5 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.01s Let me sum it up: the full test suite passes. Here's my report: tokens used 183,762 Let me sum it up: the full test suite passes. Here's my report:
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.
- Measured 2 times, so the result is not a one-off.
What did not, or is not known
- Took 22.8 minutes to install, slower than the median of the 32 comparable projects Argusic has measured.
Of the 33 agent projects Argusic has installed and timed, agnix was the 30th fastest to reach a running state, and 25 of 33 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
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Runs | 100.00 | 0.13 | |
| Argusic Runner | 1/3 | Ran out of time | 0.00 | 0.09 |
Topics (from GitHub)
agentaiai-agentsai-coding-assistantclaudeclicode-qualitycodexcopilotcursordevtoolslinterllmlspmcpopencoderustskillsvscodevscode-extension
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/agnix)Questions
- Does agnix run?
- Yes. agnix runs. Argusic installed and launched it on a clean machine in 23 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test agnix?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit e557022f0943. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test agnix?
- The run that produced this verdict cost $0.13: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does agnix take to install?
- 22.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 agnix need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing agnix?
- 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 agnix compare with the alternatives?
- Of the 33 agent projects Argusic has installed and timed, agnix was the 30th fastest to reach a running state, and 25 of 33 reached one at all.
- Where is the evidence for agnix?
- 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.