What the reviewer found
GitHub repo-management reference: 'gh secret set SSH_KEY < ~/.ssh/id_rsa' is the documented, user-invoked gh CLI feature for uploading a chosen key as an Actions secret, and the flagged curl call hits api.github.com with the user's own token to read their own account -- both are the tool's stated purpose, not exfiltration. Falling back to reading the token out of ~/.git-credentials when gh isn't installed is a real credential touchpoint worth knowing about, but it stays local to the git/GitHub workflow.
credential-access— reads credentialsnetwork— calls the vendor’s API
What was read
The file as it ships in clowlove/Hermes-House:
skills/github-repo-management/SKILL.md
What the static scan said
The scan flagged 3things. The reviewer kept 1 and dismissed 2 as false.
PE3Reaches for credential files — false positiveSC2Downloads and executes remote code — 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.