probity
TDD enforcement and guardrails for Claude Code, Codex, and GitHub Copilot CLI
Runssource: GitHubTypeScriptMITcommit fabb04968f25
TypeScript, MIT licensed. The project labels itself: agentic coding, claude code, codex, coding agent, github copilot, guardrails, hooks and policy.
probity runs. An Argusic agent installed it in 28 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
@nizos/probity v1.10.1 builds, its CLI binary (dist/bin.js) prints version and help, and all 60 test files pass (550 tests passed, 26 skipped).
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.
- System Node.js was v18.19.1 but the project requires node >=225 minutes
- Install time
- 28 minutes
- Cold machine to finish
- 2 minutes
- Errors hit and fixed
- 1 hit, 1 fixed with no human help
- How the result was proved
- vitest run exited 0: 60 test files passed, 550 passed / 26 skipped
- Model tokens used
- 17,638
- Exact commit tested
- fabb04968f25
- 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 attempt that decided the verdict above. 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.
succeeded in 130ms:
{"decision":"block","reason":"Probity: invalid hook payload: Invalid input: expected string, receiv…
The project is fully functional. Let me compile the final result.
exec
/bin/sh -lc 'cd /work/repo && export PATH=/tmp/node-v22.23.4-linux-x64/bin:$PATH && echo '"'{\"hook…
succeeded in 142ms:
{"decision":"block","reason":"Probity: invalid hook payload: Invalid input: expected string, receiv…
1.10.1
Here's the full summary of what happened and what I verified:
tokens used
17,638
Here's the full summary of what happened and what I verified: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 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.
What did not, or is not known
- Took 28 minutes to install, slower than the median of the 29 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 30 agentic-coding projects Argusic has installed and timed, probity was the 28th fastest to reach a running state, and 23 of 30 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)
agentic-codingclaude-codecodexcoding-agentgithub-copilotguardrailshookspolicytdd
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/probity)Questions
- Does probity run?
- Yes. probity runs. Argusic installed and launched it on a clean machine in 28 minutes, hitting 1 error on the way, and recorded the session.
- How did Argusic test probity?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit fabb04968f25. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test probity?
- The run that produced this verdict cost $0.03: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does probity take to install?
- 28 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 probity need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing probity?
- 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 probity compare with the alternatives?
- Of the 30 agentic-coding projects Argusic has installed and timed, probity was the 28th fastest to reach a running state, and 23 of 30 reached one at all.
- Where is the evidence for probity?
- 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.