Skip to content
Skill

Github actions hardening

Security hardening reviewer for GitHub Actions workflow files (.github/workflows/*.yml)

Install
Scripts
None
Platforms
Claude Code, Codex, Cursor
GitHub stars
41.3K
Last commit
1 day ago
License
MIT
Listing updated
today

When your agent uses it

Security hardening reviewer for GitHub Actions workflow files (.github/workflows/*.yml). Reasons about the Actions threat model that pattern matchers and general code linters miss — untrusted-input script injection, privileged triggers running fork code, mutable action references, and over-scoped tokens. Use this skill when asked to review, audit, harden, or secure a GitHub Actions workflow, when writing a new workflow, or for any request like "is this workflow safe?", "review my CI for security issues", "why is pull_request_target dangerous here?", "pin my actions", or "lock down GITHUB_TOKEN permissions". Covers script injection via ${{ }} interpolation, pull_request_target / workflow_run privilege escalation, SHA-pinning of third-party actions, least-privilege permissions, GITHUB_ENV/GITHUB_OUTPUT injection, secret exposure, OIDC over long-lived credentials, and self-hosted runner exposure on public repositories.

From the skill's SKILL.md. Your agent reads this description to decide when to load the skill.

What it can access

From a static check of its 6 files (23 KB) on GitHub on 17 November 2026. Nothing was run. Read the files before you install a skill: it can tell your agent to run anything its tools allow.

Install

Copy the skill folder to ~/.claude/skills/github-actions-hardening to use it in all your projects:

tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/github/awesome-copilot.git "$tmp" &&
mkdir -p ~/.claude/skills &&
rm -rf ~/.claude/skills/github-actions-hardening &&
cp -R "$tmp/skills/github-actions-hardening" ~/.claude/skills/github-actions-hardening &&
rm -rf "$tmp"

For one project only, put the folder in .claude/skills/github-actions-hardening inside it instead.

Claude Code docs on skills

Copy the skill folder to ~/.agents/skills/github-actions-hardening to use it in every repository:

tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/github/awesome-copilot.git "$tmp" &&
mkdir -p ~/.agents/skills &&
rm -rf ~/.agents/skills/github-actions-hardening &&
cp -R "$tmp/skills/github-actions-hardening" ~/.agents/skills/github-actions-hardening &&
rm -rf "$tmp"

For one repository only, put the folder in .agents/skills/github-actions-hardening inside it instead.

Codex docs on skills

Copy the skill folder to ~/.cursor/skills/github-actions-hardening to use it in every project:

tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/github/awesome-copilot.git "$tmp" &&
mkdir -p ~/.cursor/skills &&
rm -rf ~/.cursor/skills/github-actions-hardening &&
cp -R "$tmp/skills/github-actions-hardening" ~/.cursor/skills/github-actions-hardening &&
rm -rf "$tmp"

For one project only, put the folder in .cursor/skills/github-actions-hardening inside it instead.

Cursor docs on skills

Run in a terminal (add --scope workspace to install it for the current workspace only):

gemini skills install https://github.com/github/awesome-copilot.git --path skills/github-actions-hardening

Or copy the folder to ~/.gemini/skills/github-actions-hardening yourself.

Gemini CLI docs on skills

For GitHub Copilot in VS Code, copy the skill folder to ~/.copilot/skills/github-actions-hardening:

tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/github/awesome-copilot.git "$tmp" &&
mkdir -p ~/.copilot/skills &&
rm -rf ~/.copilot/skills/github-actions-hardening &&
cp -R "$tmp/skills/github-actions-hardening" ~/.copilot/skills/github-actions-hardening &&
rm -rf "$tmp"

For one project only, put the folder in .github/skills/github-actions-hardening inside it instead.

VS Code docs on skills

Get the folder:

git clone --depth 1 https://github.com/github/awesome-copilot.git

Then copy awesome-copilot/skills/github-actions-hardening into your agent's skills folder as github-actions-hardening. Agents that support SKILL.md read one folder per skill.

The SKILL.md format

Github actions hardening FAQ

How do I install Github actions hardening in Claude Code?

Copy the skill folder from GitHub to ~/.claude/skills/github-actions-hardening to use it in all your projects, or to .claude/skills/github-actions-hardening in one project.

Does Github actions hardening run scripts?

No. It is instructions only, with no scripts. This comes from a static check of the files on GitHub; nothing was run. Read the files before you install it.

Which AI agents can use Github actions hardening?

Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, Windsurf and Goose. Each reads skills in the SKILL.md format from its own folder; the install steps on this page list them.

What are the best alternatives to Github actions hardening?

The closest alternatives to Github actions hardening are Rea changelog update, Code review, Gem devops guidelines, Spring security and Create github issues feature from implementation plan.

More from github/awesome-copilot

  1. Design or review infrastructure, deployment, CI/CD, Docker, Kubernetes, health checks, rollback, feature flags, production readiness, and mo

    • Open source
    • 41.3K GitHub stars
    • Cloud and infrastructure
  2. Stop coding agents from shipping generic UI

    • Open source
    • 41.3K GitHub stars
  3. Cross-references C# Web API controllers/DTOs against their TypeScript/JavaScript consumers (React, Angular, Vue, Svelte, Node.js, or hand-wr

    • Open source
    • 41.3K GitHub stars
  4. Serves as a reviewer of the codebase with instructions on looking for Apple App Store optimizations or rejection reasons.

    • Open source
    • 41.3K GitHub stars
  5. Triage and resolve Arch Linux issues with pacman, systemd, and rolling-release best practices.

    • Open source
    • 41.3K GitHub stars

Alternatives to Github actions hardening

  1. Prepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Ple

    • Open source
    • 465K GitHub stars
    • Developer tools
  2. Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code follow this repo's docu

    • Open source
    • 326K GitHub stars
    • Developer tools
  3. Design or review infrastructure, deployment, CI/CD, Docker, Kubernetes, health checks, rollback, feature flags, production readiness, and mo

    • Open source
    • 41.3K GitHub stars
    • Cloud and infrastructure
  4. Configure, test and review Spring Security 6/7 in Spring Boot 3/4 apps: SecurityFilterChain lambda DSL, method security, OAuth2 resource ser

    • Open source
    • 41.3K GitHub stars
    • Security
  5. Universal SQL code review assistant that performs comprehensive security, maintainability, and code quality analysis across all SQL database

    • Open source
    • 41.3K GitHub stars
    • Databases