Is skipper-dev-workflow safe to install?

Yes — skipper-dev-workflow is safe to install, with something worth knowing. Sonnet 5 read every file skipper-dev-workflow ships from redhat-community-ai-tools/claude-plugins on 7 September 2026 and found nothing that acts against the person installing it; the static scan of its 26 rules grades it A.

Reviewed by Sonnet 5 on 7 September 2026 · a grade is what a scan and a reading found, not a guarantee · how this works

What the reviewer found

Skipper Docker build-wrapper skill. The sudo/env_reset note is a documented workaround for sudo-less Linux containers, mounting `${HOME}/.netrc:/root/.netrc` is a documented skipper.yaml option so containerized builds can reuse the user's own existing git/artifact credentials, and "Run Arbitrary Commands" just describes the tool's normal `skipper run <cmd>` build-container feature.

What was read

The file as it ships in redhat-community-ai-tools/claude-plugins:

What the static scan said

The scan flagged 3things. The reviewer kept 0 and dismissed 3 as false.

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.

Produced by agentmods.dev · Sonnet 5 · 7 September 2026

← Back to skipper-dev-workflow