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/synmux/myriad/github-actionsgit clone --depth 1 https://github.com/synmux/myriadWhat 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.00000 | $0.03510 |
| Opus 5 | $0.00000 | $0.01755 |
| Sonnet 5 | $0.00000 | $0.00702 |
| Haiku 4.5 | $0.00000 | $0.00351 |
Grade A, and why
github-actions 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 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.
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 — 261 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Actions Best Practices and Coding Standards
This guide provides comprehensive guidelines for developing efficient, reliable, secure, and maintainable GitHub Actions workflows. It covers various aspects of GitHub Actions development, including code organization, common patterns, performance considerations, security best practices, testing approaches, and tooling.
1. Code Organization and Structure
1.1 Directory Structure Best Practices
-
Workflows Directory: Store all workflow files in the
.github/workflowsdirectory. This is the standard location recognized by GitHub. -
Reusable Actions Directory (Optional): If you create custom reusable actions, consider storing them in a dedicated directory like
actions/within your repository. -
Scripts Directory (Optional): For complex workflows, you might have supporting scripts (e.g., shell scripts, Python scripts). Store these in a
scripts/directory. -
Example Directory Structure:
.github/ └── workflows/ ├── main.yml ├── deploy.yml └── release.yml actions/ ├── my-custom-action/ │ ├── action.yml │ └── index.js scripts/ ├── cleanup.sh └── build.py
1.2 File Naming Conventions
- Workflow Files: Use descriptive and consistent names for workflow files (e.g.,
deploy-staging.yml,code-analysis.yml). Avoid generic names likemain.ymlif possible, especially in repositories with multiple workflows. - Action Files: Name action files
action.ymloraction.yamlto clearly indicate their purpose. - Script Files: Use appropriate extensions for scripts (e.g.,
.shfor shell scripts,.pyfor Python scripts).
1.3 Module Organization
- Reusable Workflows: Break down complex workflows into smaller, reusable workflows using the
uses:syntax. This promotes modularity, reduces duplication, and improves maintainability. - Composite Actions: For reusable steps within a workflow, consider creating composite actions. These group multiple steps into a single action.
- Modular Scripts: If you're using scripts, organize them into modules or functions for better readability and reusability.
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 · 261 lines · 0 tokens per session scan A af4ee528c5b2
github-actions is a cursor rule published in the GitHub repository synmux/myriad (2 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,510 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
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.