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.
npx skills add pr-pm/prpm --skill github-actions-testinggit clone --depth 1 https://github.com/pr-pm/prpmWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/pr-pm/prpm/github-actions-testing)<a href="https://agentmods.dev/skills/pr-pm/prpm/github-actions-testing"><img src="https://agentmods.dev/badge/skills/pr-pm/prpm/github-actions-testing/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/pr-pm/prpm/github-actions-testing"><img src="https://agentmods.dev/badge/skills/pr-pm/prpm/github-actions-testing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 9 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Tool Misuse · line 160 Tool calls are chained to bypass individual safety checks or escalate capabilities beyond what any single tool call would allow.Fix: Limit tool chaining depth and validate the output of each tool before passing it to the next. Require explicit user approval for multi-step chains.
- high Tool Misuse · line 338 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
- medium MCP Rug Pull · line 99 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 105 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 234 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 339 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 341 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium Privilege Escalation · line 160 Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.Fix: Avoid sudo/root unless strictly required. Prefer least-privilege patterns. If elevation is needed, document the justification and scope.
- low Supply Chain · line 160 Remote code is downloaded and executed. This bypasses code review and could introduce malicious code.Fix: Avoid downloading and executing remote scripts. Use trusted packages from PyPI/npm. If remote fetch is required, verify checksums and use HTTPS.
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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00037 | $0.02618 |
| Opus 5.5 | $0.00015 | $0.01047 |
| Sonnet 5.5 | $0.00007 | $0.00524 |
| Haiku 4.5 | $0.00004 | $0.00262 |
Grade A, and why
github-actions-testing scanned grade A with 0 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 1mo 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
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:
- Pre-Push Validation: Complete workflow validation before pushing to GitHub
- Cache Configuration: Ensure cache-dependency-path is correctly specified
- Monorepo Build Order: Validate workspace dependency build sequences
- Service Container Setup: Guide proper service container configuration
- Path Validation: Verify all paths exist and are accessible
- Local Testing: Run workflows locally with act (Docker-based simulation)
- 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:
- Run actionlint on all workflow files
- Check for missing cache-dependency-path configurations
- Validate all working-directory paths exist
- Verify monorepo build order is correct
- Check service container configurations
- Provide a pre-push checklist
Debugging Workflow Failures
"My GitHub Actions workflow is failing with [error message]"
I'll:
- Analyze the error message
- Identify the root cause
- Explain why local testing didn't catch it
- Provide the correct configuration
- Show how to test the fix locally
Setup New Repository
"Set up GitHub Actions testing for my new project"
I'll:
- Install required tools (act, actionlint, yamllint)
- Create validation scripts
- Set up pre-push hooks
- Configure recommended workflows
- Provide testing procedures
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.
- 1mo ago First seen · 371 lines · 37 tokens per session scan F a83dbcb5adec
github-actions-testing is a skill published in the GitHub repository pr-pm/prpm (123 stars, last pushed 2d ago), licensed MIT. It adds 37 tokens to every session and 2,618 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
bazel-build-optimization
Optimize Bazel builds for large-scale monorepos. Use when configuring Bazel, implementing remote execution, or optimizing build performance for enterprise codebases.
release-db-config-sync
Compute the remote DB migration + Nacos config diff before a test release — apc release db-config-sync really spawns sync-test-migrations.ts --dry-run (never a stub) and diffs Nacos key dumps, stopping at the write boundary. green(0) no diff · staged(3) pending migrations/missing keys await approval · blocked(1) real…
best-practices
Transforms vague prompts into optimized Claude Code prompts. Adds verification, specific context, constraints, and proper phasing. Invoke with /best-practices.
continuous-llm-red-teaming-with-promptfoo
Wire Promptfoo and DeepTeam into CI/CD for automated regression red-teaming of LLM apps against OWASP LLM Top 10 and OWASP Agentic presets, failing the build when jailbreak or injection vulnerabilities regress.
testing-for-system-prompt-leakage
Extract and defend system prompts plus embedded secrets and routing logic.
CI/CD Pipeline Config
CI/CD pipeline configuration skill for test automation, covering GitHub Actions, Jenkins, GitLab CI, test parallelization, reporting, and artifact management.