What the reviewer found
setup-gaia post-init command, companion to gaia-init: same official astral.sh uv installer and the same scoped react-doctor cleanup rm -rf. It provisions a GitHub repo and branch protection and explicitly keeps the bot token out of the conversation/agent process ("non-negotiable safety rule"), so this is admin-gated infrastructure setup done with above-average care, not a leak.
installs-software— installs softwarenetwork— calls the vendor’s APIsettings-edit— edits agent settings
What was read
The file as it ships in gaia-react/gaia:
.claude/commands/setup-gaia.md
What the static scan said
The scan flagged 3things. The reviewer kept 1 and dismissed 2 as false.
SC2Downloads and executes remote code — false positiveRMRecursive force delete — false positiveNETMakes network calls — real
How this review was made
Sonnet 5 read the files above on 7 September 2026 and answered three questions: is it dangerous to whoever installs it, is each scanner finding real, and what should the installer know. The verdict is bound to the file's hash; when the file changes, it is scanned afresh and reviewed again. A script that changes while the definition does not is not re-reviewed — that is a known gap. How the scan and the review work.