openqodex
Open source AI code review for coding agents. A separate reviewer checks every change your agent writes before you push, in Claude Code, Codex, Cursor and Cline. No account or key of its own.
Runs with mockssource: GitHubhomepageTypeScriptApache-2.0commit 549d3301702a
TypeScript, Apache-2.0 licensed. The project labels itself: agent skills, ai agents, ai code review, claude code, claude code plugin, claude skills, cline and code quality.
openqodex runs, with stand-ins for the services it depends on. An Argusic agent installed it in 11 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
With Node 22.20.0 and pnpm 9.15.4 under $HOME/opt: install and build are clean, the CLI launches and reports 0.8.1, init installs working agent files, scan runs 8 real scanners and reports the demo's 22 planted findings, unit and e2e suites pass fully except two documented environment-version cases (git 2.43 vs 2.44, and Codex's user-namespace sandbox blocked by this container's kernel), and full review is unavailabl...
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 56 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.
- unit codex-stream test 15 failed: bwrap needs unprivileged user namespaces and this container blocks unshare (Operation not permitted)15 minutes
- e2e review-target partial-clone test failed: it asserts git >= 2.44 behavior but git here is 2.43.0; the CLI printed its documented old-git message8 minutes
- Node in container was 18.19.1 but the repo needs 22+2 minutes
- pnpm not installed1 minute
- Install time
- 11 minutes
- Cold machine to finish
- 13 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- pnpm test: 1035 passed, 6 skipped, 1 failed / 1042; pnpm test:e2e: 158 passed, 1 failed / 159; pnpm typecheck and pnpm lint exited 0; dist/bin.js --version printed 0.8.1; init installed agent files and a launcher that printed 0.8.1; demo+scan reported 22 findings across 8 real scanners; review exited 2 with the documented Full review unavailable
- Model tokens used
- 357,746
- Exact commit tested
- 549d3301702a
- 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
- Behaviour against real services
- this run was verified against stand-in services only
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
**Setup** - Node 22.20.0 installed as a prebuilt binary under `/home/runner/opt/node-v22.20.0-linux-x64` (con… - `pnpm install` clean, `pnpm build` exit 0. **What ran and what it returned** - `node packages/cli/dist/bin.js --version` printed `0.8.1`. - `pnpm test` (vitest unit): 1035 passed, 6 skipped, 1 failed out of 1042, in 72 files. - `pnpm test:e2e` (real CLI subprocess, built bundle, real scanners): 158 passed, 1 failed out of 1… - `pnpm typecheck` explicit exit 0, `pnpm lint` (oxlint) exit 0. - `doctor --install` exit 0: 11 tools ready in `/tmp/openqodex-e2e-home` (semgrep 1.94.0, gitleaks … - `openqodex demo` + `scan`: 8 scanners ran, 26 candidates, 22 findings including semgrep stripe-ke… - `openqodex init --yes --no-review`: exit 0, wrote agent files into a fresh HOME and a working run… - `openqodex review` in the demo repo: exit 2 with the documented "Full review unavailable" and the…
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
- Recovered from all 4 errors without a human stepping in, which says the failures are documented well enough to solve.
- 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
- Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
- Took 11 minutes to install, slower than the median of the 127 comparable projects Argusic has measured.
Of the 128 agent-skills projects Argusic has installed and timed, openqodex was the 109th fastest to reach a running state, and 96 of 128 reached one at all.
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 with mocks | 92.00 | 0.08 | |
| Argusic Runner | 1/3 | Did not run | 20.00 | 0.61 |
Topics (from GitHub)
agent-skillsai-agentsai-code-reviewclaude-codeclaude-code-pluginclaude-skillsclinecode-qualitycode-reviewcodexcoding-agentscursorgithub-actionslinterpre-commitsastsecret-scanningsecuritysecurity-toolsstatic-analysis
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/openqodex)Questions
- Does openqodex run?
- openqodex runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 11 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test openqodex?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 549d3301702a. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test openqodex?
- The run that produced this verdict cost $0.08: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does openqodex take to install?
- 11 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 openqodex need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing openqodex?
- 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 openqodex compare with the alternatives?
- Of the 128 agent-skills projects Argusic has installed and timed, openqodex was the 109th fastest to reach a running state, and 96 of 128 reached one at all.
- Where is the evidence for openqodex?
- 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.