reins
Stop AI agents from doing things you didn't ask for.
Runssource: GitHubhomepagePythonApache-2.0commit d5bc85ddfc9a
Python, Apache-2.0 licensed. The project labels itself: agent observability, agent security, ai monitoring, ai safety, audit trail, browser automation, claude code marketplace and claude code plugin.
reins runs. An Argusic agent installed it in 15 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
npm install and tsc build succeed, all 50 test cases pass, CLI help responds with all commands listed.
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.
- 3 scan tests expected exit code 1 but Node 18.19.1 is flagged as vulnerable by isNodeVersionVulnerable (< 22.14.0), producing EXPOSED verdict (exit code 2)2 minutes
- package.json had dangling 'winston': '^3.11.0' inside the keywords array instead of keywords array item0.5 minutes
- inquirer v9 is ESM-only but project compiles to CommonJS (tsc module: commonjs), so require() of inquirer/lib/index.js fails0.5 minutes
- Install time
- 15 minutes
- Cold machine to finish
- 17 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- node --test test/*.test.mjs passed 50/50; node dist/cli/index.js --help returned 0 with usage text
- Model tokens used
- 94,677
- Exact commit tested
- d5bc85ddfc9a
- 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.
succeeded in 13966ms: === Final verification === npm install: OK tsc build: OK Test results: # tests 50 # pass 50 # fail 0 All 50 tests pass, 0 failures. tokens used 94,677 All 50 tests pass, 0 failures.
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 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 Apache-2.0, as reported by its host.
What did not, or is not known
- Took 15 minutes to install, slower than the median of the 3 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 4 agent-observability projects Argusic has installed and timed, reins was the 4th fastest to reach a running state, and 3 of 4 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-observabilityagent-securityai-monitoringai-safetyaudit-trailbrowser-automationclaude-code-marketplaceclaude-code-pluginclaude-code-skillcuahuman-in-the-loopinterventionmcpopenclaw-security
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/reins)Questions
- Does reins run?
- Yes. reins runs. Argusic installed and launched it on a clean machine in 15 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test reins?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit d5bc85ddfc9a. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test reins?
- The run that produced this verdict cost $0.07: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does reins take to install?
- 15 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 reins need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing reins?
- 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 reins compare with the alternatives?
- Of the 4 agent-observability projects Argusic has installed and timed, reins was the 4th fastest to reach a running state, and 3 of 4 reached one at all.
- Where is the evidence for reins?
- 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.