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/audit)<a href="https://agentmods.dev/commands/8nobletruths/sabba/audit"><img src="https://agentmods.dev/badge/commands/8nobletruths/sabba/audit/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/audit"><img src="https://agentmods.dev/badge/commands/8nobletruths/sabba/audit.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.00018 | $0.00158 |
| Opus 5.5 | $0.00007 | $0.00063 |
| Sonnet 5.5 | $0.00004 | $0.00032 |
| Haiku 4.5 | $0.00002 | $0.00016 |
Grade A, and why
audit 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
Security-audit the code in: $ARGUMENTS
Use the sabba MCP tools. Prefer the token-free ones.
rankthe functions so you look at the riskiest ones first (native C/C++).huntthe target to find bugs (orsolvefor native C/C++ with Z3). Every candidate is run before it is returned, so a finding is a proof, not a guess.- Report only proven findings, each with its CWE class and the evidence. Trust nothing that did not reproduce -- there are no "possible" or "likely" findings, only proven ones.
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 · 13 lines · 18 tokens per session scan A 9a813b116eb0
audit is a command published in the GitHub repository 8NobleTruths/sabba (9 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 18 tokens to every session and 158 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
security-semgrep-setup
Check if Semgrep is installed and working. If not, install it using the best available method. Then log in to Semgrep Pro, enable the Pro engine, and run a local Pro scan in the current directory.
sessions
List all Claude Code sessions across all projects, sorted by most recent. Show project context, date, and the exact resume command for each session.
awesome-chatgpt
Search awesome-ChatGPT-repositories for open-source GitHub repositories related to ChatGPT and LLMs.
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.
pr
Handle the full workflow from current branch state to an open, CI-monitored pull request.
claude-request
Send a prompt to Claude Code via the LLM gateway with session tracking.