github-actions-testing

Guidance for checking GitHub Actions, the service that runs automated jobs such as tests and builds in a repository. It helps validate workflows before they are deployed.

In plain words
What is it for?
It is for checking and debugging workflows, including monorepos (repositories containing multiple related projects), caches, Docker-based service containers, and local workflow simulations.
Why use it?
It finds configuration mistakes that may only appear in GitHub, such as invalid paths, cache settings, dependency order, or service setup.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/pr-pm/prpm/github-actions-testing
Any agent
npx skills add pr-pm/prpm --skill github-actions-testing
Clone the repo
git clone --depth 1 https://github.com/pr-pm/prpm

Made for: Claude Code, Codex.

Per session 37 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,618 The whole file, excluding the scripts and references it only reads on demand.
Security scan F 4 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00037 $0.02618
Opus 5 $0.00018 $0.01309
Sonnet 5 $0.00007 $0.00524
Haiku 4.5 $0.00004 $0.00262

Measured 2d ago against content hash a83dbcb5adec, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade F, and why

github-actions-testing scanned grade F with 4 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Asks for rootmediumPrivilege escalation

A mod that escalates privileges can change anything on the machine, not only the project.

curl https://raw.githubusercontent.com/nektos/act/master/install.sh | sudo bash

Downloads and executes remote codehighSupply chain

curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.

curl https://raw.githubusercontent.com/nektos/act/master/install.sh | sudo bash

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

rm -rf packages/*/dist

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl https://raw.githubusercontent.com/nektos/act/master/install.sh | sudo bash
.claude/skills/github-actions-testing/SKILL.md · 371 lines

How it starts

The opening of the file, as written. The whole thing — 371 lines — stays where its author put it; the contents beside it link to each section on GitHub.

SKILL: GitHub Actions Testing & Validation Expert

Description

Interactive expert for testing and validating GitHub Actions workflows before deployment. Prevents common CI failures by catching cache configuration errors, path issues, monorepo dependency problems, and service container configuration mistakes.

Capabilities

This skill provides:

  1. Pre-Push Validation: Complete workflow validation before pushing to GitHub
  2. Cache Configuration: Ensure cache-dependency-path is correctly specified
  3. Monorepo Build Order: Validate workspace dependency build sequences
  4. Service Container Setup: Guide proper service container configuration
  5. Path Validation: Verify all paths exist and are accessible
  6. Local Testing: Run workflows locally with act (Docker-based simulation)
  7. Static Analysis: Lint workflows with actionlint and yamllint

When to Use This Skill

Invoke this skill when:

  • Creating or modifying GitHub Actions workflows
  • Debugging workflow failures in CI
  • Setting up new repositories with CI/CD
  • Migrating to monorepo architecture
  • Adding service containers to workflows
  • Experiencing cache-related failures
  • Getting "module not found" errors in CI but not locally

Usage

Quick Validation

"Validate my GitHub Actions workflows before I push"

I'll:

  1. Run actionlint on all workflow files
  2. Check for missing cache-dependency-path configurations
  3. Validate all working-directory paths exist
  4. Verify monorepo build order is correct
  5. Check service container configurations
  6. Provide a pre-push checklist

Debugging Workflow Failures

"My GitHub Actions workflow is failing with [error message]"

I'll:

  1. Analyze the error message
  2. Identify the root cause
  3. Explain why local testing didn't catch it
  4. Provide the correct configuration
  5. Show how to test the fix locally

Setup New Repository

"Set up GitHub Actions testing for my new project"

I'll:

  1. Install required tools (act, actionlint, yamllint)
  2. Create validation scripts
  3. Set up pre-push hooks
  4. Configure recommended workflows
  5. Provide testing procedures

Read the full file on GitHub · 371 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 371 lines · 37 tokens per session scan F a83dbcb5adec

Subscribe to this mod's changes

github-actions-testing is a skill published in the GitHub repository pr-pm/prpm (120 stars, last pushed 2mo ago), licensed MIT. It adds 37 tokens to every session and 2,618 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it F with 4 findings (asks for root, downloads and executes remote code, recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.