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.
npx agentmods add commands/gaia-react/gaia/distribution-auditgit clone --depth 1 https://github.com/gaia-react/gaiaWrote 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/gaia-react/gaia/distribution-audit)<a href="https://agentmods.dev/commands/gaia-react/gaia/distribution-audit"><img src="https://agentmods.dev/badge/commands/gaia-react/gaia/distribution-audit.svg" alt="Measured on agentmods" 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 | $0.00055 | $0.01807 |
| Opus 5 | $0.00028 | $0.00903 |
| Sonnet 5 | $0.00011 | $0.00361 |
| Haiku 4.5 | $0.00006 | $0.00181 |
Grade A, and why
distribution-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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/distribution-audit
Maintainer-only. Thin orchestrator over .gaia/cli/gaia-maintainer, which owns every deterministic step. This command supplies the one thing the CLI cannot: a human answering, file by file, whether a newly-shipping file should ship or be withheld.
.gaia/release-exclude is the distribution boundary: a file ships to adopters if and only if git tracks it and no line in that file masks it. .gaia/manifest.json is the update policy /update-gaia consumes, and incidentally the ledger of which shipping files a maintainer has acknowledged. A file that git tracks, that no exclude line masks, and that the manifest does not yet list is "unanswered": it would ship, but nobody has said so on purpose.
Pre-flight: Worktree check
This command drives the release CLI's manifest regeneration and answers the shipping boundary for the clone. If invoked from a linked worktree, reject hard: gaia_refuse_if_worktree (.gaia/scripts/main-only-lib.sh) asks the shared resolver which tree this is and refuses out loud, naming the main checkout, when the answer is a worktree.
Detection (run this first, before anything else):
. .gaia/scripts/main-only-lib.sh
gaia_refuse_if_worktree "/distribution-audit" || exit 1
If the detection does not fire, fall through to ## Step 1. Find the unanswered files below.
Step 1. Find the unanswered files
.gaia/cli/gaia-maintainer release manifest --check --json
--check is read-only. It exits non-zero whenever it finds any of six conditions, so capture stdout and parse it as JSON regardless of the exit code; a non-zero exit here is not a failure, it is the normal signal that something needs attention. The payload shape is:
{"missing": [{"expected": "owned", "file": ".gaia/statusline/example.sh"}], "extra": [], "drift": [], "versionDrift": null, "classifierOverlaps": [], "scanScopeGaps": []}
missing is an array of objects, not of path strings: the path lives in .file, and .expected is the update class the classifier would assign. Extract paths with:
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.
- 3d ago First seen · 94 lines · 55 tokens per session scan A e01319e191b9
distribution-audit is a command published in the GitHub repository gaia-react/gaia (22 stars, last pushed 3d ago), licensed MIT. It adds 55 tokens to every session and 1,807 once invoked, about $0.0003 per session on Opus 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
review-renovate
Review and merge renovate PRs with automerge configuration updates.
push-and-release
Git pull, resolve conflicts, push, fix hook errors, then release.
release
Perform a full release: generate release notes, bump version, commit, tag, and push.
release
Ship a stable cmux release built by CI: bump version, update changelog, open a PR, merge, tag, then GitHub Actions builds, signs, and publishes.
release
Prepare a release by updating docs and bumping the version.
release-now
Create a git tag + GitHub Release for open-pr — an official release if standing on main, an RC if standing on a branch with an open PR (a dev tool specific to this repo, not shipped in the plugin).