What the reviewer found
A troubleshooting guide for the Mycelium CLI: the curl command fetches Mycelium's own official install.sh from its own GitHub Pages domain, sudo starts the local Docker daemon, and the rm -rf targets only the tool's own ~/.mycelium config directory as a documented 'reset everything' step. Nothing reaches outside the machine or the tool's own directory.
installs-software— installs softwarenetwork— calls the vendor’s API
What was read
The file as it ships in mycelium-io/mycelium:
.claude/skills/troubleshooting/SKILL.md
What the static scan said
The scan flagged 4things. The reviewer kept 0 and dismissed 4 as false.
PE2Asks for root — false positiveSC2Downloads and executes remote code — false positiveRMRecursive force delete — false positiveNETMakes network calls — false positive
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.