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 agentmods add rules/pr-pm/prpm/github-actions-testinggit clone --depth 1 https://github.com/pr-pm/prpmWhat 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 | $0.02605 | $0.02605 |
| Opus 5 | $0.01303 | $0.01303 |
| Sonnet 5 | $0.00521 | $0.00521 |
| Haiku 4.5 | $0.00261 | $0.00261 |
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 yesterday.
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 How it starts
The opening of the file, as written. The whole thing — 369 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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.
- yesterday First seen · 369 lines · 2,605 tokens per session scan F 324ee420055d
github-actions-testing is a cursor rule published in the GitHub repository pr-pm/prpm (120 stars, last pushed 2mo ago), licensed MIT. It adds 2,605 tokens to every session, about $0.0130 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.
Other cursor rules, from other repositories
00-core-agent
Core instructions defining the AI assistant's persona, response format, general coding principles, communication guidelines, and specialized mode management.
Accessibility-Review
Reviews web interfaces, content, or code snippets for common accessibility (a11y) issues based on WCAG guidelines, ensuring usability for people with disabilities.
Security-Audit
Reviews code, configurations, or architecture designs for common security vulnerabilities and adherence to security best practices, referencing standards like OWASP Top 10.
ShadcnUI
Best practices and guidelines for working with shadcn/ui components across various frameworks.
Supabase
Guidelines for using Supabase Auth, Database (Postgres migrations), Storage, Realtime, Edge Functions, and AI/Vectors.
API-Docs
Generates or refines API reference documentation, detailing endpoints, parameters, request/response formats, authentication methods, and error codes. Focuses on technical accuracy and developer usability.