Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
/plugin marketplace add nizos/probitynpx agentmods add plugins/nizos/probity/marketplacegit clone --depth 1 https://github.com/nizos/probityGrade A, and why
probity scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"name": "probity",
"owner": {
"name": "Nizar Selander"
},
"plugins": [
{
"name": "probity",
"source": "./",
"description": "TDD enforcement and guardrails for Claude Code, Codex, and GitHub Copilot CLI."
}
]
}
What ships with it
1 file beside marketplace.json in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2d ago First seen · 14 lines scan A bb100e6c0cc9
probity is a plugin published in the GitHub repository nizos/probity (187 stars, last pushed 16d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other plugins, from other repositories
tdd-guard
Automated Test-Driven Development enforcement.
tdd-guard
Plugin marketplace listing 1 plugin: tdd-guard.
makoto
Plugin marketplace listing 1 plugin: makoto.
makoto
Holds Claude Code to its word — every claim checked against the agent's own logged record; faked checks blocked, not warned (four narrow advisory self-checks excepted). Two-tier catalog (15 pre-checks, 19 Stop gates), each shipped at measured zero false positives.
agentlint
Plugin marketplace listing 1 plugin: agentlint.
agentlint
Claude Code marketplace wrapper for AgentLint's AI-agent guardrail engine. 77 rules across 8 packs, hybrid AgentChute security feeds, circuit-breaker visibility, inline-ignore reasons.