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.
git clone --depth 1 https://github.com/ivangrynenko/cursorrulesWrote 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/rules/ivangrynenko/cursorrules/github-actions-standards)<a href="https://agentmods.dev/rules/ivangrynenko/cursorrules/github-actions-standards"><img src="https://agentmods.dev/badge/rules/ivangrynenko/cursorrules/github-actions-standards/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/rules/ivangrynenko/cursorrules/github-actions-standards"><img src="https://agentmods.dev/badge/rules/ivangrynenko/cursorrules/github-actions-standards.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00000 | $0.00526 |
| Opus 5.5 | $0.00000 | $0.00210 |
| Sonnet 5.5 | $0.00000 | $0.00105 |
| Haiku 4.5 | $0.00000 | $0.00053 |
Grade A, and why
github-actions-standards 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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Actions Standards
Ensures GitHub Actions workflows follow best practices and use the latest action versions.
Rule Details
-
Name: github_actions_standards
-
Description: Enforce standards for GitHub Actions workflows
Filters
- file extension pattern:
\\.ya?ml$ - file path pattern:
\\.github/workflows/
Enforcement Checks
- Conditions:
- pattern
uses:\\s*actions/upload-artifact@v[123]– Use actions/upload-artifact@v4 instead of older versions. Version 3 is deprecated: https://github.blog/changelog/2024-04-16-deprecation-notice-v3-of-the-artifact-actions/ - pattern
uses:\\s*actions/download-artifact@v[123]– Use actions/download-artifact@v4 instead of older versions. - pattern
uses:\\s*actions/checkout@v[12]– Consider using actions/checkout@v4 for the latest features and security updates.
- pattern
Suggestions
- Guidance: GitHub Actions Best Practices:
- Latest Action Versions: Always use the latest stable versions of GitHub Actions.
actions/checkout@v4actions/upload-artifact@v4actions/download-artifact@v4actions/setup-node@v4actions/setup-python@v5
- Workflow Structure: Organize workflows with clear job names and step descriptions.
- Caching: Implement caching for dependencies to speed up workflows.
- Security: Use
GITHUB_TOKENwith minimum required permissions. - Artifacts: Use descriptive names for artifacts and set appropriate retention periods.
- Matrix Strategy: Use matrix builds for testing across multiple environments.
- Timeouts: Set appropriate timeouts for jobs to prevent hanging workflows.
Validation Checks
- Conditions:
- pattern
uses:\\s*actions/upload-artifact@v4– Good job using the latest version of actions/upload-artifact! - pattern
uses:\\s*actions/download-artifact@v4– Good job using the latest version of actions/download-artifact! - pattern
uses:\\s*actions/checkout@v[34]– Good job using a recent version of actions/checkout!
- pattern
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 · 52 lines · 0 tokens per session scan A b02771a0b120
github-actions-standards is a cursor rule published in the GitHub repository ivangrynenko/cursorrules (88 stars, last pushed 11mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 526 tokens. 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 cursor rules, from other repositories
turborepo
Turborepo: monorepo structure, caching, task pipelines.
ci-cd
CI/CD: pipelines, deployment, automation.
beanstalk-deploy
Robust deployment patterns for Elastic Beanstalk with GitHub Actions, Pulumi, and edge case handling.
wire-ci
CI pipeline setup with bundled, forge-neutral templates and local validation. Detects the forge from the git remote, generates workflows for supported forges, and skips honestly for the rest. The CI equivalent of wire-observability.
deploy
Build → verify artifact → deploy → wait → smoke deployment pipeline. Platform-agnostic (MCP or CLI), with configurable timeout, retry with exponential backoff, and integrated health-check. The deploy half of CI/CD: run after build to push to production.
yaml-config
Rules for YAML / config / infra files (Docker, K8s, Terraform, GitHub Actions, etc.).