Borrowing it
Nothing to install: this file belongs to gaia-react/gaia. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/gaia-react/gaia/main/.claude/commands/distribution-vet.mdgit 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-vet)<a href="https://agentmods.dev/commands/gaia-react/gaia/distribution-vet"><img src="https://agentmods.dev/badge/commands/gaia-react/gaia/distribution-vet/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/gaia-react/gaia/distribution-vet"><img src="https://agentmods.dev/badge/commands/gaia-react/gaia/distribution-vet.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.00060 | $0.03317 |
| Opus 5.5 | $0.00024 | $0.01327 |
| Sonnet 5.5 | $0.00012 | $0.00663 |
| Haiku 4.5 | $0.00006 | $0.00332 |
Grade A, and why
distribution-vet 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 10d 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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/distribution-vet
Maintainer-only. Thin orchestrator over .gaia/cli/gaia-maintainer, which owns every deterministic step. This command supplies the one thing the CLI cannot: a classification of each newly-shipping file against the written distribution boundary, and a maintainer's answer on the few the taxonomy does not settle.
Contents: Step 1. Find the unanswered files; Step 2. Decide which path applies; Step 3. Classify against the categories, then ask only what needs asking; Step 4. Apply every answer in one call; What this command never does.
.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.
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 five 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": [], "regionDrift": []}
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:
jq -r '.missing[].file'
missing is not "everything that ships." The paths in ADOPTER_OWNED_SENTINELS (.gaia/cli/src/release/manifest.ts: .gaia/manifest.json, .gaia/packages.json, .gaia/VERSION, and wiki/log.md) are permanent adopter-owned fixtures that ship with baseline content but are never classified, so they never enter missing and this command never asks about them. That is correct, not a gap.
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.
- 10d ago Changed · -18 lines d841e5004d3b
- 11d ago Changed e42eede158ac
- 13d ago Changed 3baf78ebf8d1
- 14d ago Changed · +2 lines 698a2bc8c97b
- 15d ago Changed · -2 lines f5323da1bded
- 16d ago First seen · 171 lines · 60 tokens per session scan A 673d2f5770d2
distribution-vet is a command published in the GitHub repository gaia-react/gaia (26 stars, last pushed 4d ago), licensed MIT. It adds 60 tokens to every session and 3,317 once invoked, about $0.0002 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-10-14.
Other commands, from other repositories
sdlc
Route a task to the next synced SDLC workflow based on current artifacts and repo state.
brainstorm-feature
SDLC intake that turns a rough idea into an approved BRD-lite brief (Why lane) or delivery contract (Direction lane) at docs/brd/brd-[slug].md, sized by SNC tier.
plan-feature
Plan a feature from BRD-lite brief or clear intent into PRD (What), decisions, implementation plan, and task slices.
verify-work
Verify feature, bug, UI, API, mobile, security, or deployment work against acceptance criteria.
discover-product
Discover and frame product opportunities using verified customer and market evidence, strategic authority, and explicit non-goals.
review-product-value
Review realized product value against registered measurement contracts and baseline evidence, separating delivery completion from causal ROI.