security

Configure GitHub Actions workflows with least-privilege permissions and input sanitization.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/xiaolai/awful-for-claude --skill security-xiaolai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security
Source: https://github.com/xiaolai/awful-for-claude/tree/main/skills/awful/security
Command: npx skills add https://github.com/xiaolai/awful-for-claude --skill security-xiaolai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Security model for awful workflows. GitHub Actions agents run with real credentials and can modify repos, post comments, and create PRs. Security is not optional.

Core Features & Use Cases

  • Principle of least privilege: default read-only; only grant write permissions that the specific agent explicitly needs.
  • Fork PR protection and safe-outputs guidance; prevent credential exposure and code execution risks.
  • Input sanitization and per-workflow permissions enforcement.

Quick Start

Configure the default agent permissions to enforce least-privilege across workflows.

Frequently Asked Questions about security

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

FAQPage Schema
How do I enforce least privilege permissions in GitHub Actions?

Fork PR protection in GitHub Actions prevents credential exposure by applying safe-outputs configurations and input sanitization, restricting what external contributors can execute or modify when triggering workflows.

How do I restrict GitHub Actions agents from modifying repositories?

You can restrict GitHub Actions agents by applying per-workflow permissions and enforcing a read-only default, ensuring agents only gain write access to explicitly required resources like comments or PRs.

Why do GitHub Actions workflows need input sanitization for issue comments?

GitHub Actions workflows need input sanitization for issue comments to prevent code execution risks and credential exposure, ensuring that triggers from issues and labels cannot inject malicious commands into the workflow.

What are the limitations of using least-privilege models for GitHub Actions?

A limitation of the least-privilege model for GitHub Actions is that overly restrictive per-workflow permissions may break automated PR creation or comment posting if the specific write permissions required are not explicitly granted.