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/abderrahimghazali/cursor-rulesWrote 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/abderrahimghazali/cursor-rules/github-actions-standards)<a href="https://agentmods.dev/rules/abderrahimghazali/cursor-rules/github-actions-standards"><img src="https://agentmods.dev/badge/rules/abderrahimghazali/cursor-rules/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/abderrahimghazali/cursor-rules/github-actions-standards"><img src="https://agentmods.dev/badge/rules/abderrahimghazali/cursor-rules/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.00577 |
| Opus 5.5 | $0.00000 | $0.00231 |
| Sonnet 5.5 | $0.00000 | $0.00115 |
| Haiku 4.5 | $0.00000 | $0.00058 |
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.
What it actually says
GitHub Actions Standards
Ensures GitHub Actions workflows follow best practices and use the latest action versions.
actions:
-
type: enforce conditions:
-
pattern: "uses:\s*actions/upload-artifact@v[123]" message: "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]" message: "Use actions/download-artifact@v4 instead of older versions."
-
pattern: "uses:\s*actions/checkout@v[12]" message: "Consider using actions/checkout@v4 for the latest features and security updates."
-
-
type: suggest message: | 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.
- Latest Action Versions: Always use the latest stable versions of GitHub Actions.
-
type: validate conditions:
-
pattern: "uses:\s*actions/upload-artifact@v4" message: "Good job using the latest version of actions/upload-artifact!"
-
pattern: "uses:\s*actions/download-artifact@v4" message: "Good job using the latest version of actions/download-artifact!"
-
pattern: "uses:\s*actions/checkout@v[34]" message: "Good job using a recent version of actions/checkout!"
-
metadata: priority: high version: 1.0 tags: - ci/cd - github - automation
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 · 65 lines · 0 tokens per session scan A 1d37aa467dee
github-actions-standards is a cursor rule published in the GitHub repository abderrahimghazali/cursor-rules (2 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 577 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-31.
Other cursor rules, from other repositories
release
Changesets release pipeline - version PR and its dispatched CI check, shared vX.Y.Z tag, CI gate before tagging, release:check gate, Dependabot changesets, no npm publish, GITHUBTOKEN tag trigger limitation.
ci
CI parity with pnpm run ci, expression-context rules for env blocks, affected vs full graph by event, frozen lockfile, lockfile-keyed store cache, SHA pins, zizmor, deny-by-default permissions.
vortex-cicd-standards
Standards for Vortex CI/CD and Renovate configuration.
git-and-commits
Conventional Commits; offer copy-paste commit after functional work.
100-dev-tools
Configure development tools when bootstrapping repository to ensure code quality, consistent commits, and automated workflows.
creating-cursor-rules
Meta-rule for creating effective Cursor IDE rules with best practices, patterns, and examples.