StarSling Skills

---
name: ci-secure
description: >-
  Scans a repo's GitHub Actions workflows for the ten critical CI/CD
  attack vectors — template injection, fork code executed with privileges
  (pwn requests), cache poisoning, impostor action SHAs, secrets dumps,
  GITHUB_ENV hijack, write-token untrusted triggers, credentials in
  caches/artifacts, unverified remote code execution (curl|bash and
  mutable fetch-and-run), and dependency install scripts
  running in a job that holds secrets — reports every finding
  with a plain-English attacker scenario, plus pass/fail config
  hygiene checks, and fixes selected findings via per-finding
  subagents. Deliberately NOT comprehensive — critical
  exploit-chain checks only (references/why-these-ten.md).
  Use when: the user asks to audit or review CI/CD or GitHub Actions
  security posture, "is my CI secure", "audit my CI security", or names
  ci-secure / /ci-secure. Do NOT trigger for: CI speed, cost, or
  wall-clock audits ("why is CI slow") — use ci-speedup; CI config
  best-practices grading ("grade my CI", "CI score") — use ci-score.
license: MIT
---

# CI Secure

Scans `.github/workflows/*.yml` against the **ten critical attack vectors**
in [references/security-patterns.md](references/security-patterns.md) — each
a complete outsider → compromise path with real incidents behind it (the
selection criterion and rejection record:
[references/why-these-ten.md](references/why-these-ten.md)). Every finding
renders with a "what an attacker could do" scenario; **zero findings is a
first-class result**. The skill asks which findings to fix and dispatches one
subagent per finding group. It never commits, pushes, or opens a PR
**unasked** — by default the user reviews the working-tree diff themselves.

**Scope honesty (verbatim, in every report):** *Critical exploit-chain checks
only — this is not a comprehensive audit.*

**Prereqs:** PyYAML (`pip install pyyaml` — the scanner's only third-party
dep). `gh` is optional, used for the network-gated impostor-SHA check (P14.11
— the one vector that cannot be answered from YAML alone), the dormancy note,
and six config facts read over the API (required checks skippable, fork-PR
approval, CODEOWNERS enforced, two environment checks, secrets). Everything