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.
git clone --depth 1 https://github.com/8NobleTruths/sabbaWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/8nobletruths/sabba/prove-fix)<a href="https://agentmods.dev/commands/8nobletruths/sabba/prove-fix"><img src="https://agentmods.dev/badge/commands/8nobletruths/sabba/prove-fix/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/8nobletruths/sabba/prove-fix"><img src="https://agentmods.dev/badge/commands/8nobletruths/sabba/prove-fix.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00019 | $0.00141 |
| Opus 5.5 | $0.00008 | $0.00056 |
| Sonnet 5.5 | $0.00004 | $0.00028 |
| Haiku 4.5 | $0.00002 | $0.00014 |
Grade A, and why
prove-fix 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 1mo 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
Prove the change in $ARGUMENTS actually works -- do not claim it does until it is proven.
Call sabba prove with a test command that captures the behavior the change is supposed to
produce (for example a specific test, or a command that should now succeed). Proven means the
test FAILS on the git base and PASSES on the working tree -- that is the difference between "the
model says it works" and "it works".
Report proven true or false with the reason. If it is not proven, the change is not done.
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.
- 1mo ago First seen · 12 lines · 19 tokens per session scan A 8b595b8b38df
prove-fix is a command published in the GitHub repository 8NobleTruths/sabba (9 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 19 tokens to every session and 141 once invoked, about $0.0001 per session on Opus 5.5. 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 commands, from other repositories
expect
Diff-aware AI browser testing — reads the git diff, maps changes to affected pages via the route map, generates a targeted test plan, and executes it via agent-browser (Rust daemon + CDP, ARIA-tree-first) with pass/fail reporting. Use when testing UI changes, verifying PRs before merge, or running regression checks on…
fire-verify-uat
Conversational User Acceptance Testing with automatic parallel diagnosis on failures.
tdd
Test-driven change — write the failing test first, then implement.
story-and-test
For the component(s) in scope.
fire-test
Run Dominion Flow plugin integration tests to verify all commands and integrations work correctly.
t00-playwright-test
A command for testing a locally running web app in a real browser with Playwright, a browser automation and testing tool. It checks normal user flows and selected edge cases, then reports results with screenshots.