ci-security-review

Review CI/CD workflows for unsafe permissions, untrusted input, and secret exposure.

Updated Jun 15, 2026
One-click install
npx skills add https://github.com/ravenslight2010/Production-run-calculator --skill ci-security-review-ravenslight2010
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ci-security-review
Source: https://github.com/ravenslight2010/Production-run-calculator/tree/main/.agents/skills/ci-security-review
Command: npx skills add https://github.com/ravenslight2010/Production-run-calculator --skill ci-security-review-ravenslight2010

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? CI/CD pipelines run with privileged credentials and are a common attack surface, yet workflow misconfigurations like overprivileged tokens, untrusted input interpolation, and unpinned actions often go unnoticed until exploited. This Skill performs a structured, read-only security review of GitHub Actions and similar CI workflows before they cause damage. ## Core Features & Use Cases - Untrusted Execution Analysis: Detects pull_request_target abuse, fork-controlled code execution with privileged tokens, and unsafe interpolation of branch names, PR text, or dispatch inputs into shell scripts. - Permissions, Secrets, and Provenance Checks: Audits job-level permissions, secret scoping, OIDC usage, third-party action pinning to commit SHAs, and cache/artifact trust boundaries. - Repository Publication Review: Distinguishes first-public from version-release reviews, checking full reachable Git history, tags, and release assets for committed secrets before visibility changes. - Use Case: Before merging a new deploy workflow, run this Skill to flag floating action tags, cross-trust cache restoration, and credential-bearing artifacts, then receive a severity-ranked report with minimal safe remediations. ## Quick Start Ask the assistant to perform a read-only security review of the GitHub Actions workflows in this repository and report findings by severity.

Frequently Asked Questions about ci-security-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review GitHub Actions workflows for security issues?▼

Inventory all workflow files, triggers, job permissions, secrets, third-party actions, and artifact flows, then check each against known risk patterns like untrusted input in run scripts and overprivileged tokens. This Skill automates that checklist and produces a severity-ranked report.

What is the risk of pull_request_target in GitHub Actions?▼

pull_request_target runs with the base repository's privileged token and secrets, so checking out or executing fork-controlled code under it lets untrusted contributors access write tokens and credentials. Validation of untrusted contributions must be separated from privileged jobs.

Should I pin GitHub Actions to commit SHAs or tags?▼

Pin third-party actions and reusable workflows to immutable commit SHAs, since tags and branches are mutable and can be repointed to malicious code. Record the human-readable release version alongside the pinned SHA for maintainability.

Is it safe to make a private GitHub repository public if the current files are clean?▼

No. Scanning only the current working tree is insufficient because reachable Git history, old tags, branches, and release assets may still contain committed secrets. A committed credential counts as exposure even if later deleted and must be rotated.

Can this Skill test a workflow exploit to confirm a vulnerability?▼

No. The review is strictly read-only: it does not trigger workflows, change repository settings, or produce exploit payloads. It proposes static inspection or an explicitly authorized isolated test instead.